| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Three CI workflows that need only `contents: read` permissions and no other permissions did not have explicit permissions set, and would therefore be given default permissions configured for the repository, which might be more expansive than the workflows need. It is recommended to set explicit workflow permissions [1]. This does that, specifying permissions as `pythonpackage.yml` already did, and closing three `actions/missing-workflow-permissions` CodeQL alerts (new since gitpython-developers#2032 enabled scanning of GHA workflows). [1]: https://codeql.github.com/codeql-query-help/actions/actions-missing-workflow-permissions/
This change is analogous to gitpython-developers/GitPython#2033. See also gitpython-developers/smmap#60.
This change is analogous to gitpython-developers/GitPython#2033. See also gitpython-developers/gitdb#121.
This change is analogous to gitpython-developers/GitPython#2033. See also gitpython-developers/smmap#60.
| Back | FazBrowse Home | New Git URL |
Specify explicit contents: read workflow permissions
Three CI workflows that need only contents: read permissions and no other permissions did not have explicit permissions set, and would therefore be given default permissions configured for the repository, which might be more expansive than the workflows need.
It is recommended to set explicit workflow permissions. This does that, specifying permissions as pythonpackage.yml already did, and closing three actions/missing-workflow-permissions CodeQL alerts (new since #2032 enabled scanning of GHA workflows).
I'll merge this once I verify that all CI checks still pass.