Conversation
The command was right and its report was two of six.
2 workflow(s) have never succeeded, across 1603 run(s).
1541 Auto Merge Ready PRs
62 Coq Proofs Validation
4 more have never succeeded but fall under --min-runs 50:
16 Lean proofs
8 Brain Seal Refresh
4 Vivado Synth (Docker, GH-hosted)
2 Build Vivado Docker Image
9 registration(s) are `active` to the API with no file in the tree --
history, not a gate, and nothing to fix:
31 .github/workflows/format-check.yml
7 Formal (Yosys)
...
Two defects, opposite in direction.
The floor DROPPED four silently. `--min-runs` exists so a new or rarely-triggered
workflow is not called dead, which is right, and the four it hid include
`brain-seal-refresh.yml`: eight lifetime runs across five months, every one
rejected with GH013 because its last step pushes to master and this repository's
own ruleset requires a pull request (#2915). Few runs is not few enough to be
safe -- a structurally impossible workflow fails every time it runs, and runs
rarely. They are now named under the report rather than dropped from it.
The `active` filter ADDED nine. GitHub keeps a workflow registered as active
after its file is deleted: 61 registrations here against 48 files. Those nine
have never succeeded and there is nothing to fix in any of them; one carries 31
failures, more than four of the six real ones, so run count alone put a phantom
above the workflow that cannot work by construction.
`classify` decides deleted FIRST, for that reason, and its mutation -- deciding
the floor first -- fails `a_deleted_workflow_is_history_at_any_run_count`.
The path check applies only when a single repository is asked about, since it
reads the working tree; for any other repo the API's word stands.
Refs #2914
Refs #2915
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-29 23:23:14 UTC
Summary
Seal Status
|
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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.
The command already asked this question. Its report was 2 of 6.
Two defects, opposite in direction
The floor dropped four silently.
--min-runsexists so a new orrarely-triggered workflow is not called dead — right, and the four it hid include
brain-seal-refresh.yml: 8 lifetime runs across five months, every onerejected, because its last step is a
git pushto master and rulesett27-master-protectionanswersGH013 … Changes must be made through a pull request(#2915). Few runs is not few enough to be safe: a structurallyimpossible workflow fails every time it runs, and runs rarely.
The
activefilter added nine. GitHub keeps a workflow registeredactiveafter its file is deleted — 61 registrations against 48 files. One of the
nine carries 31 failures, more than four of the six real ones, so ordering by run
count alone put a phantom above the workflow that cannot work by construction.
Why
classifydecides deleted firstA registration with no file cannot be under- or over-run — there is nothing to
fix either way. Letting the run count decide its bucket files a phantom under
whichever threshold it happens to meet. The mutation that reverses the order
fails
a_deleted_workflow_is_history_at_any_run_count.a_deleted_workflow_is_history_at_any_run_countunder_the_floor_is_a_bucket_and_not_a_silenceThe path check applies only when a single repository is asked about, since it
reads the working tree; for any other repo the API's word stands.
Refs #2914
Refs #2915