ci: avoid duplicate compiler audit after PR merge - #70
Merged
Merged
Conversation
oisee
enabled auto-merge
October 2, 2026 16:58
PR tests: 🟢 passCommit:
The external CZECH and full Zork I stories are not part of this PR gate. |
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 compiler assertion matrix, fuzz jobs, and sweep currently run once on the PR merge tree and again immediately after merge on
main. That duplicate main run competes with the next PR for GitHub runners. Keep the full compiler checks on PRs, where branch protection now requires the blocking jobs, and in the nightly audit; leave the existing fast PR gate on both PRs and main pushes.Validation: workflow YAML parses, and
git diff --checkpasses. GitHub CI on this PR will validate the workflow call. The changed condition applies only to the duplicatemainpush.