-
Notifications
You must be signed in to change notification settings - Fork 112
chore: use reusable tox workflow #2057
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
base: main
Are you sure you want to change the base?
Conversation
| uses: ansible/team-devtools/.github/workflows/tox.yml@main | ||
| secrets: inherit | ||
| with: | ||
| min_python: "3.10" | ||
| default_python: "3.13" | ||
| max_python: "3.13" | ||
| other_names: | | ||
| pkg | ||
| lint | ||
| docs | ||
| py314-devel |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 2 months ago
To fix the problem, insert a permissions: section at the root of the workflow, immediately after the name: (and before on:), limiting the permissions of the GITHUB_TOKEN to the minimum needed. Since this workflow delegates the actual job to a remote workflow, it is safest to set a minimal default here, such as contents: read. If more specific write privileges are needed, they should be added as required. In this case, adding permissions: contents: read at the start of the workflow should mitigate the risk and adhere to CodeQL's recommendation.
-
Copy modified lines R2-R3
| @@ -1,4 +1,6 @@ | ||
| name: tox | ||
| permissions: | ||
| contents: read | ||
|
|
||
| on: | ||
| create: # is used for publishing to PyPI and TestPyPI |
|
Moving to draft due to CI failures. |
Pull request was converted to draft
No description provided.