Add CI workflow to check for unintended executable permissions in scripts #67
Conversation
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
smuppand
force-pushed
the
main
branch
2 times, most recently
from
791d3d4 to
e0f0ea1
Compare
…file modes Adds a GitHub Actions workflow to validate that only explicitly intended files (like run.sh or executable binaries) have executable permissions. This helps prevent accidental commits of files with incorrect modes (e.g., *.md, *.txt marked as executable). The check runs on each PR and fails the job if any suspicious file permission is detected, improving repo hygiene and review quality. Exemptions (e.g., run.sh) can be controlled by editing the allowlist. Signed-off-by: Srikanth Muppandam <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR introduces a GitHub Actions workflow: check-executable-permissions.yml, which scans all tracked files in pull requests to ensure only expected files have executable (+x) permissions.
🔒 Why this is useful:
Prevents accidental commits with chmod +x on README.md, docs, or config files.
Enforces consistent permissions across the repository.
Avoids noisy diffs and review confusion caused by file mode changes.
✅ Allowlisted files (example):
run.sh
Any known executable under scripts/ or utils/
You can update the allowlist inside the workflow file if needed.