Skip to content

ci: gate merging on a single Release Validation summary job #774

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

Closed
elijahbenizzy wants to merge 1 commit into from
+6 −4
Closed

ci: gate merging on a single Release Validation summary job #774

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
10 changes: 6 additions & 4 deletions .asf.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,12 @@ github:
required_status_checks:
# strict means "Require branches to be up to date before merging".
strict: false
# contexts are the names of checks that must pass
contexts:
- "Release Validation / build-artifacts"
- "Release Validation / install-and-smoke (3.12)"
# No required contexts — the Release Validation workflow still runs on
# every PR (and on tags) so failures are visible in the checks UI, but
# we don't gate merging on it. Path-filtered docs/website PRs were
# getting permanently blocked because GitHub treats SKIPPED jobs as
# non-passing for required-status-checks.
contexts: []
required_pull_request_reviews:
dismiss_stale_reviews: false
require_code_owner_reviews: false
Expand Down
Loading