Potential fix for code scanning alert no. 1: Workflow does not contain permissions #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/jpmorby/taskman/security/code-scanning/1
In general, the problem is fixed by explicitly declaring a
permissions:block that restricts theGITHUB_TOKENto the minimal scopes required. For this workflow, the steps only need to read repository contents (foractions/checkout) and do not appear to require any write access to GitHub resources such as contents, pull requests, or issues.The best fix, without changing existing functionality, is to add a
permissions:block at the workflow root (top-level, alongsidename:andon:). This will apply to all jobs in the workflow, includingci, and limit the token to read-only on repository contents. Concretely, in.github/workflows/tests.yml, add:between the
name: testsline and theon:block. No other changes are needed; all existing steps (checkout, setup, install, build, tests, linting) will continue to work, because they only require read access to the repository.Suggested fixes powered by Copilot Autofix. Review carefully before merging.