Closed ConnorJC3 closed 2 months ago
Suggestion: Could we follow the best-practice of commenting why you need each permission as seen in the kubernetes-sigs/karpenter project?
Added comments to all the permissions that aren't read: contents
. I can add them there if people want, but as that permissions is necessary to checkout the repo it would just be # Checkout repo
on every action.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: torredil
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
@ElijahQuinones: changing LGTM is restricted to collaborators
Is this a bug fix or adding new feature?
"Bug fix"
What is this PR about? / Why do we need it?
The
kubernetes-sigs
GitHub org was moved to a GitHub enterprise account, changing the default permissions for actions. Explicitly define the permissions we need in each action so they continue to run successfully.What testing is done?
CI