Potential fix for code scanning alert no. 1: Workflow does not contain permissions #5
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.
Potential fix for https://github.com/reflex-dev/reflex-azure-auth/security/code-scanning/1
In general, the fix is to explicitly declare a minimal
permissionsblock in the workflow so the automatically provided GITHUB_TOKEN has only the scopes required. For this workflow, the job just checks out code and runs pre‑commit locally, so it only needs read access to repository contents.The best fix without changing existing functionality is to add a
permissionssection scoped to thepre-commitjob (or at the root). To keep the change minimal and localized to the flagged region, we’ll add it directly underpre-commit:in.github/workflows/pre-commit.yml. We’ll setcontents: read, which is sufficient foractions/checkoutand running checks. No additional imports or methods are needed since this is a YAML workflow definition.Concretely: in
.github/workflows/pre-commit.yml, underjobs: pre-commit:, insert a newpermissions:block beforetimeout-minutes: 30, indented to match job-level keys. No other lines need to change.Suggested fixes powered by Copilot Autofix. Review carefully before merging.