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.
feat(governance): reject workflows with duplicate YAML keys #582
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
feat(governance): reject workflows with duplicate YAML keys #582
Changes from all commits
6fb71c7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Uh oh!
There was an error while loading. Please reload this page.
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.
💡 Edge Case: Unhashable complex mapping keys crash with uncaught TypeError
_no_duplicates constructs each key and does
key in mapping/mapping[key] = .... If a workflow uses a complex YAML key (a mapping or sequence key), construct_object returns an unhashable dict/list and the membership/assignment raises TypeError, which is not caught by the yaml.YAMLError/OSError handlers in check() and aborts the whole run. This is unlikely in real workflows but would make the linter itself crash rather than report cleanly; wrap the dict operations or catch TypeError.Fix:
Was this helpful? React with 👍 / 👎
Check failure on line 61 in scripts/check-workflow-duplicate-keys.py
LLMs running this code with faulty CLI arguments can escape file system restrictions. Refactor this code to validate the constructed path before accessing the file system.
Uh oh!
There was an error while loading. Please reload this page.
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.
💡 Edge Case: Any YAML syntax error is mislabeled as a duplicate key
check() catches every yaml.YAMLError (including plain syntax/scanner errors, not just the duplicate-key error raised by _no_duplicates), and the summary printed on failure asserts the files "contain duplicate keys" and that "yaml.safe_load does NOT catch this." A file with an unrelated parse error will therefore be reported as a duplicate-key violation, misdirecting the fix. Consider raising a dedicated exception subclass from _no_duplicates and only attributing the duplicate-key message when that specific error is caught, otherwise report it as a generic parse error.
Use a distinct exception so genuine syntax errors are not mislabeled.:
Was this helpful? React with 👍 / 👎
Check failure on line 76 in scripts/check-workflow-duplicate-keys.py
LLMs running this code with faulty CLI arguments can escape file system restrictions. Refactor this code to validate the constructed path before accessing the file system.
Uh oh!
There was an error while loading. Please reload this page.