Branch protection (via Gitea API): master now requires the status check CI / build + unit + e2e (pull request) to be successful before a PR can be merged. Verified with a throwaway PR (#29, closed unmerged): a normal merge attempt returns 405 "Not all required status checks successful".
Auto-merge: the merge API supports merge_when_checks_succeed — queueing a PR (POST /pulls/{n}/merge with body {"do":"merge","merge_style":"merge","merge_when_checks_succeed":true}) makes Gitea merge it automatically once CI goes green. Verified live: this exact flow merged the documentation PR (#30, v0.19.1).
AGENTS.md change-process item 5 now documents both (v0.19.1), so future work queues auto-merge instead of merging manually.
Done — two parts:
1. **Branch protection** (via Gitea API): `master` now requires the status check **CI / build + unit + e2e (pull request)** to be successful before a PR can be merged. Verified with a throwaway PR (#29, closed unmerged): a normal merge attempt returns 405 "Not all required status checks successful".
2. **Auto-merge**: the merge API supports `merge_when_checks_succeed` — queueing a PR (`POST /pulls/{n}/merge` with body `{"do":"merge","merge_style":"merge","merge_when_checks_succeed":true}`) makes Gitea merge it automatically once CI goes green. Verified live: this exact flow merged the documentation PR (#30, v0.19.1).
`AGENTS.md` change-process item 5 now documents both (v0.19.1), so future work queues auto-merge instead of merging manually.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
But can be set to automerge.
Edit gitea workflow.
Done — two parts:
masternow requires the status check CI / build + unit + e2e (pull request) to be successful before a PR can be merged. Verified with a throwaway PR (#29, closed unmerged): a normal merge attempt returns 405 "Not all required status checks successful".merge_when_checks_succeed— queueing a PR (POST /pulls/{n}/mergewith body{"do":"merge","merge_style":"merge","merge_when_checks_succeed":true}) makes Gitea merge it automatically once CI goes green. Verified live: this exact flow merged the documentation PR (#30, v0.19.1).AGENTS.mdchange-process item 5 now documents both (v0.19.1), so future work queues auto-merge instead of merging manually.