mirror of
https://github.com/gopher64/gopher64.git
synced 2026-04-26 15:35:58 +03:00
[PR #414] [CLOSED] Potential fix for code scanning alert no. 3: Workflow does not contain permissions #496
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gopher64#496
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/gopher64/gopher64/pull/414
Author: @loganmc10
Created: 6/3/2025
Status: ❌ Closed
Base:
main← Head:alert-autofix-3📝 Commits (1)
3abb31cPotential fix for code scanning alert no. 3: Workflow does not contain permissions📊 Changes
1 file changed (+3 additions, -0 deletions)
View changed files
📝
.github/workflows/build.yml(+3 -0)📄 Description
Potential fix for https://github.com/gopher64/gopher64/security/code-scanning/3
To fix the issue, we need to add a
permissionsblock to the workflow. This block should specify the least privileges required for the workflow to function. Based on the actions used in the workflow, the minimal permissions required arecontents: read. This will ensure that the workflow can interact with the repository contents without granting unnecessary write access.The
permissionsblock can be added at the root level of the workflow to apply to all jobs, or it can be added to each job individually. In this case, adding it at the root level is sufficient and simplifies the configuration.Suggested fixes powered by Copilot Autofix. Review carefully before merging.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.