Skip to content

Commit 28e836e

Browse files
authored
ci(verify): open promotion PRs against TechAPI develop (#50)
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.
1 parent d486b06 commit 28e836e

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

.github/workflows/verify-network.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,10 @@ jobs:
4545
with:
4646
repository: GetTechAPI/TechAPI
4747
path: TechAPI
48+
# TechAPI follows git-flow: promotions are integration work, so branch
49+
# from develop and open the PR there. Cutting from main would put the
50+
# bot branch behind whatever is already integrated.
51+
ref: develop
4852
fetch-depth: 0
4953
token: ${{ secrets.TECHENGINEBOT_TOKEN || secrets.TECHAPI_TOKEN || secrets.GITHUB_TOKEN }}
5054

@@ -121,6 +125,6 @@ jobs:
121125
Auto-promotions from the verification layer (green+live-source or crossref-confirm).
122126
Each flip is verified:false->true only; see data/_verify/ledger.jsonl. Refs #1"
123127
git push origin "$branch"
124-
gh pr create --repo GetTechAPI/TechAPI --base main --head "$branch" \
128+
gh pr create --repo GetTechAPI/TechAPI --base develop --head "$branch" \
125129
--title "data(verify): verified promotions ($(date -u +%Y-%m-%d))" \
126130
--body "Automated verified promotions from \`app.verify promote\` (run in TechEngine). Each change flips only the \`verified\` flag; structural validator passed and diff scope guarded. Review before merge. Refs #1"

0 commit comments

Comments
 (0)