main is protected and .gitea/workflows/check.yml runs script/cibuild (docker build, which runs make check) on every push
and pull request targeting main. What has not been verified is
whether the branch protection rule actually lists the Check job as a
required status check — i.e. whether a PR with a red build is blocked
from merging, or merely decorated.
TODO.md calls this out under Future Steps: "Confirm .gitea/workflows/check.yml gates merges on make check so main cannot
regress."
Steps:
inspect the branch protection settings for main in the Gitea repo
settings (requires repo admin)
if status-check enforcement is off, enable it and add the check
job of the Check workflow to the required checks list
verify empirically: open a PR (any open lint-fix PR works), confirm
the merge button is blocked until the workflow passes
Definition of done:
branch protection for main requires the Check workflow to pass
before merge
verified on a real PR (screenshot or comment noting the observed
blocked/unblocked state)
outcome recorded in a comment on this issue
`main` is protected and `.gitea/workflows/check.yml` runs
`script/cibuild` (docker build, which runs `make check`) on every push
and pull request targeting `main`. What has not been verified is
whether the branch protection rule actually lists the `Check` job as a
required status check — i.e. whether a PR with a red build is blocked
from merging, or merely decorated.
`TODO.md` calls this out under Future Steps: "Confirm
`.gitea/workflows/check.yml` gates merges on make check so main cannot
regress."
Steps:
- inspect the branch protection settings for `main` in the Gitea repo
settings (requires repo admin)
- if status-check enforcement is off, enable it and add the `check`
job of the `Check` workflow to the required checks list
- verify empirically: open a PR (any open lint-fix PR works), confirm
the merge button is blocked until the workflow passes
Definition of done:
- branch protection for `main` requires the `Check` workflow to pass
before merge
- verified on a real PR (screenshot or comment noting the observed
blocked/unblocked state)
- outcome recorded in a comment on this issue
clawbot
added this to the 1.1.0 milestone 2026-08-07 18:41:07 +02:00
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.
mainis protected and.gitea/workflows/check.ymlrunsscript/cibuild(docker build, which runsmake check) on every pushand pull request targeting
main. What has not been verified iswhether the branch protection rule actually lists the
Checkjob as arequired status check — i.e. whether a PR with a red build is blocked
from merging, or merely decorated.
TODO.mdcalls this out under Future Steps: "Confirm.gitea/workflows/check.ymlgates merges on make check so main cannotregress."
Steps:
mainin the Gitea reposettings (requires repo admin)
checkjob of the
Checkworkflow to the required checks listthe merge button is blocked until the workflow passes
Definition of done:
mainrequires theCheckworkflow to passbefore merge
blocked/unblocked state)
clawbot referenced this issue2026-09-03 18:29:27 +02:00