You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @cowtowncoder, I'm Pedro and I'm back (see #896) hoping to offer a bit more help with security enhancements.
This time around, I'd like to suggest you add top-level permissions to your workflows. This is equivalent to the work done in #792, but for cifuzz.yml and release.yml. Yes, I forgot to put top-level permissions on the workflow I submitted in my last PR. 🤦♂️
I'm sending a PR with these changes alongside this issue to keep things simple.
These top-level permissions are necessary because workflows run with an underlying GITHUB_TOKEN that, by default, comes with write-all permissions. However, this default can be modified to read-only. If you prefer doing this (I'd recommend so, in order to future proof against any other well-meaning workflows that accidentally forget to add top-level permissions...), follow these steps:
Hey @cowtowncoder, I'm Pedro and I'm back (see #896) hoping to offer a bit more help with security enhancements.
This time around, I'd like to suggest you add top-level permissions to your workflows. This is equivalent to the work done in #792, but for
cifuzz.yml
andrelease.yml
. Yes, I forgot to put top-level permissions on the workflow I submitted in my last PR. 🤦♂️I'm sending a PR with these changes alongside this issue to keep things simple.
These top-level permissions are necessary because workflows run with an underlying GITHUB_TOKEN that, by default, comes with write-all permissions. However, this default can be modified to read-only. If you prefer doing this (I'd recommend so, in order to future proof against any other well-meaning workflows that accidentally forget to add top-level permissions...), follow these steps:
This basically makes all workflows without top-level permissions run with
instead of the default
If a workflow ever needs broader permissions, they can be set at the top level or job level without a problem.
The text was updated successfully, but these errors were encountered: