From 4c0b1e5328073bc1e9a21f493e06a3588e63eb1a Mon Sep 17 00:00:00 2001 From: Seungpyo1007 Date: Fri, 31 Jul 2026 18:24:07 +0900 Subject: [PATCH] ci(verify): open promotion PRs against TechAPI develop MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- .github/workflows/verify-network.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/verify-network.yml b/.github/workflows/verify-network.yml index 71a8660..92da15f 100644 --- a/.github/workflows/verify-network.yml +++ b/.github/workflows/verify-network.yml @@ -45,6 +45,10 @@ jobs: with: repository: GetTechAPI/TechAPI path: TechAPI + # TechAPI follows git-flow: promotions are integration work, so branch + # from develop and open the PR there. Cutting from main would put the + # bot branch behind whatever is already integrated. + ref: develop fetch-depth: 0 token: ${{ secrets.TECHENGINEBOT_TOKEN || secrets.TECHAPI_TOKEN || secrets.GITHUB_TOKEN }} @@ -121,6 +125,6 @@ jobs: Auto-promotions from the verification layer (green+live-source or crossref-confirm). Each flip is verified:false->true only; see data/_verify/ledger.jsonl. Refs #1" git push origin "$branch" - gh pr create --repo GetTechAPI/TechAPI --base main --head "$branch" \ + gh pr create --repo GetTechAPI/TechAPI --base develop --head "$branch" \ --title "data(verify): verified promotions ($(date -u +%Y-%m-%d))" \ --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"