fix(ci): push the verification status refresh to TechAPI develop - #56
Merged
Conversation
The job checks out TechAPI's default branch — develop since the git-flow switch — commits the refreshed status.json there, then pushed HEAD:main. main has not moved since, so the push is rejected as non-fast-forward and every run fails after doing all the work: status.json on develop is stale since 2026-07-31. Push to develop, pin the checkout ref so it cannot drift from the push target again, and rebase first since several bots write to develop and a status refresh is not worth failing over a race. (bump-techapi.yml's HEAD:main is correct — that one pushes to TechEngine's own main, which has no develop.) Refs #1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
verify-statuschecks out TechAPI's default branch —developsince the git-flow switch — commits the refreshedstatus.jsonthere, and then pushesHEAD:main.mainhas not moved since, so the push is rejected and every run fails after doing all of its work:data/_verify/status.jsonon develop is consequently stale since 2026-07-31 — it still reports 14,777 verified when the real figure is 20,777, and it is what the homepage renders.Change
HEAD:developref: developon the TechAPI checkout so the branch worked on cannot drift from the push target againgit pull --rebase origin developfirst, since several bots write to develop and a status refresh is not worth failing over a racebump-techapi.ymlalso pushesHEAD:main, and that one is correct — it targets TechEngine's ownmain, which has nodevelop.This is the last of the git-flow leftovers; the same class of fix as #54 (weekly-ingest) and #50 (promotion PRs).
Refs #1