The main rule sets status_check_contexts: ["Lint"], but Actions reports contexts like Lint / JS (eslint) (push) and Lint / Secret scan (gitleaks) (pull_request). No context is ever named exactly Lint, so every PR into main is unmergeable ("Not all required status checks successful"), even with all checks green. matrix #12 had to be merged by direct push.
Fix: in Settings → Branches → main, set the required checks to the real names, or to a pattern like Lint / * (Gitea supports glob patterns there).
The `main` rule sets `status_check_contexts: ["Lint"]`, but Actions reports contexts like `Lint / JS (eslint) (push)` and `Lint / Secret scan (gitleaks) (pull_request)`. No context is ever named exactly `Lint`, so **every PR into `main` is unmergeable** ("Not all required status checks successful"), even with all checks green. matrix #12 had to be merged by direct push.
Fix: in Settings → Branches → `main`, set the required checks to the real names, or to a pattern like `Lint / *` (Gitea supports glob patterns there).
The main branch protection now requires the status-check pattern Lint / * instead of Lint, which matched no check (the real contexts are Lint / JS (eslint) (push), Lint / Shell (shellcheck) (pull_request) and so on). The rest of the rule is unchanged: status checks are on, and push is allow-listed to jared.
Verified: PR #15 merged through Gitea's own merge (API), with all 14 Lint / … checks (push and pull_request) green. Before the fix, every PR into main failed with "Not all required status checks successful".
## Fixed
The `main` branch protection now requires the status-check pattern **`Lint / *`** instead of `Lint`, which matched no check (the real contexts are `Lint / JS (eslint) (push)`, `Lint / Shell (shellcheck) (pull_request)` and so on). The rest of the rule is unchanged: status checks are on, and push is allow-listed to `jared`.
**Verified:** PR #15 merged through Gitea's own merge (API), with all 14 `Lint / …` checks (push and pull_request) green. Before the fix, every PR into `main` failed with "Not all required status checks successful".
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.
The
mainrule setsstatus_check_contexts: ["Lint"], but Actions reports contexts likeLint / JS (eslint) (push)andLint / Secret scan (gitleaks) (pull_request). No context is ever named exactlyLint, so every PR intomainis unmergeable ("Not all required status checks successful"), even with all checks green. matrix #12 had to be merged by direct push.Fix: in Settings → Branches →
main, set the required checks to the real names, or to a pattern likeLint / *(Gitea supports glob patterns there).Fixed
The
mainbranch protection now requires the status-check patternLint / *instead ofLint, which matched no check (the real contexts areLint / JS (eslint) (push),Lint / Shell (shellcheck) (pull_request)and so on). The rest of the rule is unchanged: status checks are on, and push is allow-listed tojared.Verified: PR #15 merged through Gitea's own merge (API), with all 14
Lint / …checks (push and pull_request) green. Before the fix, every PR intomainfailed with "Not all required status checks successful".