Git Environment Promotion
Verify gate
- Confirm review, change ownership, validation evidence, remote, branch, environment, permission, and rollback policy.
- Commit only the owned and verified scope, then push the configured test branch/remote.
- Deploy or promote to the registered test environment and run smoke plus the applicable module/E2E checks.
- Record commit, remote, branch, deployment identity, evidence, failures, and rollback in
流程管理/GitPromotion.mdthroughdoc-git-promotion.
Final gate
- Require user acceptance and explicit production authorization.
- Merge/tag/push according to the registered release policy.
- Promote the approved artifact to production; run production smoke/E2E/monitoring checks.
- Update GitPromotion, Release, Environment, Validation, Acceptance, task, risk, and version records.
Vercel routing
For Vercel projects, use the available Vercel Skills as applicable: vercel:vercel-cli, vercel:deployments-cicd, vercel:verification, and vercel:observability or vercel:vercel-api when live inspection is required.
Safety
- A Hook may block closeout for missing evidence but must never auto-commit, auto-push, auto-deploy, or infer production authorization.
- If destination, credentials, permission, rollback, or environment identity is missing, record the blocker and stop before mutation.


