ci(ingest): open the weekly ingest PR against TechAPI develop - #54
Merged
Conversation
weekly-ingest was the last automation still targeting main. TechAPI follows git-flow — pushing to main deploys the site and notifies TechEngine — so a 6,900-file data PR landing there bypasses the release gate that every other data path goes through. The checkout already resolved to develop implicitly (it is the default branch); pin it explicitly so the base and the branch point cannot drift apart if the default changes again. 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
1 participant
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.
weekly-ingestwas the last automation still opening its PR with--base main. TechAPI follows git-flow — a push tomainfires the Pages deploy and the TechEngine notification — so a ~6,900-file ingest PR landing there bypasses the release gate every other data path goes through. TechAPI#147 is the current example.--base main→--base developref: developexplicitly so the base and the branch point cannot drift apart if the default ever changes againMatches what
verify-network.ymland TechAPI'sbump-engine.ymlalready do.Refs #1