Repository navigation
fix: gh-merge-green requires ci-status only when a workflow defines it #17357
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.
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
986dff5
test: gh-merge-green merges a repo whose ci.yml has no ci-status job …
teamleaderleo 1171cec
fix: gh-merge-green requires ci-status only when a workflow defines it
teamleaderleo 8b6a13d
fix: gh-merge-green fails closed on empty workflow content and reads …
teamleaderleo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Replace the regex YAML detection with a real YAML parser.
The pattern
^\s+['"]?ci-status['"]?\s*:matches any indentedci-status:key at any depth. This includes keys underwith:orenv:, and text inside arun: |block. It does not match flow-stylejobs: {ci-status: ...}.A false positive requires a check that no job produces, so merges block. A false negative skips the aggregate gate.
Parse the YAML and test for
ci-statusunder the top-leveljobsmapping. If PyYAML is missing, fail closed with a clear error.Proposed direction
Also catch
yaml.YAMLErrorand exit 0 so the script still requiresci-status.Based on learnings: "require a real YAML parser library (e.g., PyYAML in Python) rather than a regex-based fallback."
📝 Committable suggestion
🤖 Prompt for AI Agents
Source: Learnings