ci: fix workflow disabling to avoid parse-failure noise - #5
Merged
Merged
Conversation
Commenting out entire workflow files (from #3/#4) made GitHub treat them as invalid workflows, causing a parse-time failure run on every push instead of just not running. Restoring valid YAML here; these are disabled properly via the Actions API (gh workflow disable) instead, which suppresses triggering without producing failure runs and is reversible with gh workflow enable. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014HN3f74pyFnr7MeRFMeCEt
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.
Follow-up to #3/#4. Commenting out entire workflow files made GitHub treat them as invalid, so each push produced a red "failure" run for every disabled workflow (auto-assign-pr, deploy_check, etc.) — noise that looked like a real CI break.
What changed
gh workflow disable(GitHub's native Actions toggle) after merge, which fully suppresses triggering with no failure runs, and is reversible withgh workflow enable.How to test
mastershows no runs at all for the 12 disabled workflows, and no failure status for them.🤖 Generated with Claude Code
https://claude.ai/code/session_014HN3f74pyFnr7MeRFMeCEt