In the Commit and push if changed step of the Crawl Course Availability action runner, if the only net change detected is the timestamp update (but no other data), we can probably add a short-circuit to refrain from pushing a commit in that case (or some "stability" threshold of, say, five checks/attempts showing only timestamp changes results in no subsequent commits until another non-timestamp change is detected). Not a high priority fix/change (or arguably necessary at all), but I figured I'd document it here anyways.
In the
Commit and push if changedstep of theCrawl Course Availabilityaction runner, if the only net change detected is the timestamp update (but no other data), we can probably add a short-circuit to refrain from pushing a commit in that case (or some "stability" threshold of, say, five checks/attempts showing only timestamp changes results in no subsequent commits until another non-timestamp change is detected). Not a high priority fix/change (or arguably necessary at all), but I figured I'd document it here anyways.