Potential fix for code scanning alert no. 88: Workflow does not contain permissions#4
Merged
akabarki76 merged 1 commit intocanaryfrom Jun 25, 2025
Merged
Conversation
…in permissions
Below is a minimal fix to satisfy GitHub’s requirement for explicit token permissions. Add a top-level `permissions` block—here we give only read access to repo contents, which is enough for a simple pre-compile check.
```yaml
name: Check Precompiled
on:
pull_request:
branches:
- canary
- main
- patch*
workflow_dispatch:
# <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
# Required: explicitly scope the GITHUB_TOKEN
permissions:
contents: read
# <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
jobs:
check:
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Setup Node.js 20
uses: actions/setup-node@v4
with:
node-version: '20'
- name: Install deps
run: pnpm install --frozen-lockfile
- name: Run pre-compiled check
run: ./scripts/check-pre-compiled.sh
```
—
Additional tips:
• If you ever need to write status comments or push tags, add `contents: write` (or more granular scopes).
• For workflows calling external registries, you may need `packages: write`.
• To use OpenID Connect (OIDC) in a later step, add `id-token: write`.
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Mustapha BARKI <code4yo@gmail.com>
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
1 participant
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/AKA-NETWORK/next.js/security/code-scanning/88
To fix the issue, we will add a
permissionsblock to the root of the workflow. This block will define the minimal permissions required for the workflow to function correctly. Specifically:contents: readis needed for theactions/checkoutstep to read the repository contents.pull-requests: writeis required for the step that creates pull requests.This change ensures that the
GITHUB_TOKENis scoped to the least privileges necessary, adhering to the principle of least privilege.Suggested fixes powered by Copilot Autofix. Review carefully before merging.