Skip to content

ci: correct the gate comment — backend-ci-gate is now required on main #2269

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
JSv4 merged 1 commit into from
Aug 21, 2026
Merged

ci: correct the gate comment — backend-ci-gate is now required on main #2269

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
11 changes: 6 additions & 5 deletions .github/workflows/backend.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,11 +293,12 @@ jobs:
# leaves a red linter mergeable (a job skipped by its own `if:` reports
# SUCCESS to branch protection, and a red linter skips pytest).
#
# NOT YET REQUIRED as of this commit: `main` has no `required_status_checks`
# object at all, so merging this job gates nothing by itself. Turn it on
# with .github/scripts/require_backend_ci_gate.sh --apply, and check with
# `gh api repos/{owner}/{repo}/branches/main/protection` whether that has
# happened rather than assuming this comment is current.
# Required on `main` as of 2026-08-20 (PR #2267). Note `enforce_admins` is
# false, so an admin can still bypass it. Re-apply or move it with
# .github/scripts/require_backend_ci_gate.sh --apply, and confirm the
# current state with
# `gh api repos/{owner}/{repo}/branches/main/protection`
# rather than assuming this comment is still accurate.
#
# `if: always()` is what makes this requirable: it reports on every PR,
# including ones where every job above it was skipped.
Expand Down
Loading