Add permissions: {} to all reusable workflows#148114
Add permissions: {} to all reusable workflows#148114ezio-melotti merged 1 commit intopython:mainfrom
permissions: {} to all reusable workflows#148114Conversation
|
Thanks @ezio-melotti for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14. |
|
Sorry, @ezio-melotti, I could not cleanly backport this to |
|
Sorry, @ezio-melotti, I could not cleanly backport this to |
|
GH-148115 is a backport of this pull request to the 3.14 branch. |
|
GH-148116 is a backport of this pull request to the 3.13 branch. |
|
Thanks @ezio-melotti for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
|
Thanks @ezio-melotti for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Thanks @ezio-melotti for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
|
Sorry, @ezio-melotti, I could not cleanly backport this to |
|
Sorry, @ezio-melotti, I could not cleanly backport this to |
|
Sorry, @ezio-melotti, I could not cleanly backport this to |
|
GH-148122 is a backport of this pull request to the 3.12 branch. |
|
GH-148123 is a backport of this pull request to the 3.11 branch. |
Add permissions: {} to all reusable workflows
(cherry picked from commit 1f36a51)
This PR explicitly adds
permissions: {}to all reusable workflows, solving a number of CodeQL issues.Technically, this is not strictly needed, since the reusable workflows inherits the permissions of the caller, however doing so has 3 advantages:
I also tightened the permissions of a few workflows that had
permissions: contents: read, and tested on my fork that everything still works fine.