Skip to content

fix(ci): push the verification status refresh to TechAPI develop #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Seungpyo1007 merged 1 commit into from
Aug 6, 2026
Merged

fix(ci): push the verification status refresh to TechAPI develop #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions .github/workflows/verify-status.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: verify-status
# Keep TechAPI's data/_verify/status.json (the verification-state aggregate: how
# many records are verified + Tier 0 bands per category) current. Runs in
# TechEngine against a TechAPI checkout and commits the refreshed file back to
# TechAPI main as TechEngineBot. Fires when TechAPI main changes (relayed by
# TechAPI develop as TechEngineBot. Fires when TechAPI main changes (relayed by
# TechAPI's notify-engine -> techapi-updated) and daily as a backstop. The
# "commit only if changed" guard means the status commit can't loop.
on:
Expand Down Expand Up @@ -35,6 +35,9 @@ jobs:
with:
repository: GetTechAPI/TechAPI
path: TechAPI
# TechAPI follows git-flow. This already resolved to develop as the
# default branch — pin it so it cannot drift from the push target.
ref: develop
token: ${{ secrets.TECHENGINEBOT_TOKEN || secrets.TECHAPI_TOKEN || secrets.GITHUB_TOKEN }}

- uses: actions/setup-python@v6
Expand All @@ -57,4 +60,7 @@ jobs:
git config user.name "TechEngineBot"
git config user.email "289859915+TechEngineBot@users.noreply.github.com"
git commit -m "chore(verify): refresh verification status aggregate"
git push origin HEAD:main
# Rebase first: several bots write to develop, and a status refresh is
# never worth failing the run over a race.
git pull --rebase origin develop
git push origin HEAD:develop
Loading