Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Github Actions: set top level permissions #242

Merged
merged 2 commits into from
Apr 19, 2024

Conversation

psilva-veeam
Copy link
Contributor

There's the recommendation to set top level permission e.g. by setting contents: read and settings needed write permissions (already there) at the job level

Comment on lines +3 to +4
permissions:
contents: read
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@psilva-veeam Makes sense. Also, these are the default permissions for the GH token for this repo, these are enforced.

@julio-lopez julio-lopez merged commit aae6644 into master Apr 19, 2024
4 checks passed
@julio-lopez julio-lopez deleted the gh_actions_top_level_permission branch April 19, 2024 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants