Potential fix for code scanning alert no. 1: Workflow does not contain permissions#27
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#27
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #27 +/- ##
=======================================
Coverage 94.28% 94.28%
=======================================
Files 2 2
Lines 140 140
=======================================
Hits 132 132
Misses 6 6
Partials 2 2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
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/jferrl/go-githubauth/security/code-scanning/1
The best way to fix this issue is to explicitly set the
permissionskey near the top of the workflow file. Since the workflow only needs to read the repository contents for building (and does not need to write to contents, issues, packages, or any other GitHub entity), it should setcontents: readas the minimal required permission. The safest and simplest fix is to add this top-levelpermissionsblock directly under the workflow'sname, so it applies to all jobs. No change to imports or functionality is needed—just a single block addition.Suggested fixes powered by Copilot Autofix. Review carefully before merging.