Add CI workflow to check for unintended executable permissions in scripts #67
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.