ci: block new Python files via PR check#5600
Merged
marsninja merged 16 commits intojaseci-labs:mainfrom Apr 20, 2026
Merged
Conversation
SandeepaHWP
changed the title
Member
|
add a label to ignore this check! |
Member
|
combine them to single sub jobs |
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
3 participants
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.
Summary
Adds a GitHub Actions workflow that fails any PR introducing new
.pyfiles.What it does:
.pyfiles are being added (--diff-filter=Acatches additions only)To skip this check:
Add the
skip-no-python-checklabel to your PR. The check will re-run automatically when the label is added and will pass.And 3 quick parallel jobs were merged into one for better readability of checks.