Conversation
`tri census pin --gate` runs here, and this workflow is not one of the four required contexts -- so a red census cannot block a merge, and a squash-merge never runs the local hook that would otherwise catch it. "Make it required" would have broken the repository twice over, and both were measured before anything was changed. The job was displayed as `build`. So are the jobs in `build-vivado-image.yml` and `coq-kernel.yml`. GitHub matches a required check by CONTEXT, so requiring `build` names three workflows: satisfiable by the wrong one, or hanging on one that did not run. It is `cli-tri` now, and `build` is not among the four current required contexts, so nothing depended on the old name. And it was paths-filtered on `pull_request`. A required context that does not POST is not passed -- it is pending forever. Over the last 40 merged PRs, 15 (38%) touched none of the filtered paths and every one would have hung. Cost of running on every PR, measured rather than estimated: +38% of runs on a job whose median is 2.9 minutes, green 58 of its last 60 (43 of 45 on pull_request). A gate that reddens rarely is one that can be required. The `push:` filter is kept: a master baseline only needs taking when the subject moves. The ruleset is NOT touched. That is a settings change and the owner's alone; this turns it into one safe click instead of a change that hangs 38% of PRs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
gHashTag
enabled auto-merge
September 6, 2026 17:56
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #3386
tri census pin --gateruns in this workflow, and it is not one of the four required contexts — so a red census cannot block a merge, and a squash-merge never runs the local hook either.3429f9c6merged red for both reasons at once."Make it required" would have broken the repository twice over, and both were measured before anything changed.
1. The context name was not unique
The job was displayed as
build. So are the jobs inbuild-vivado-image.ymlandcoq-kernel.yml. GitHub matches a required check by context, sorequire: buildnames three workflows — satisfiable by the wrong one, or hanging on one that did not run.Verified
buildis not among the four current required contexts, so nothing depended on the old name.2. It was paths-filtered, so requiring it would hang most PRs
A required context that does not POST is not "passed" — it is pending forever.
Measured over the last 40 merged PRs: 15 (38%) touched none of the filtered paths, and every one would have hung.
Cost of the fix, measured rather than estimated
pull_request)A gate that reddens rarely is one that can be required. The
push:filter is kept — a master baseline only needs taking when the subject moves.What this does not do
The ruleset is untouched. Adding
cli-trito the required set is a repository-settings change and the owner's alone. This turns it into one safe click instead of a change that hangs 38% of pull requests.