ci(verify): open promotion PRs against TechAPI develop - #50
Merged
Conversation
TechAPI has adopted git-flow (GetTechAPI/TechAPI#141): main is the released state that publishes the site, develop is where integration lands. The promotion bot writes data, so it belongs on develop. Checks out TechAPI at develop as well as targeting it — cutting the bot branch from main would place it behind whatever is already integrated, and the resulting PR would drag those commits along.
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.
What
TechAPI has adopted git-flow (TechAPI#141):
mainis the released state that publishes the site and triggers the engine handshake,developis where integration lands. The verified-promotion bot writes data into TechAPI, so it belongs ondevelop.gh pr create --base main→--base developref: developBoth are needed together. Targeting
developwhile still branching frommainwould cut the bot branch from behind whatever is already integrated, and the PR would drag those unrelated commits in with it.Nothing else changes: promotions still run on the weekly schedule, still write only
verifiedflags, and still open a human-gated PR.YAML parses.