feat: add explicit permissions to GitHub workflows #985
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.
Context
GitHub Actions workflows should follow the principle of least privilege by declaring explicit permissions rather than relying on default permissions. This reduces attack surface and improves security posture.
Related Jira ticket
N/A
Screenshots
N/A
Changes
Added explicit
permissions: contents: readdeclarations to workflows that only need repository read access:.github/workflows/ci.yml- CI workflow for builds, lints, and tests on PRs.github/workflows/copilot-setup-steps.yml- Setup validation workflowThe
release.ymlworkflow already had appropriate permissions defined (contents: read,pages: write,id-token: write) for its deployment operations.All workflows now explicitly declare their required permissions rather than inheriting default GITHUB_TOKEN permissions.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.