ci: declare contents:read on CI Tests workflow#29
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
CI Tests runs checkstyle + pytest against the matrix; no GitHub API calls beyond `actions/checkout`. Pinning the workflow to contents:read documents that and brings ci.yaml in line with publish-nightly.yml and publish-release.yml, which already carry job-level permissions blocks. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
chore/ci-permissions
branch
from
98127ad to
4122110
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The CI Tests workflow only runs lint and tests. It doesn't open issues, push commits, attach release artifacts, or invoke OIDC. Right now it inherits whatever
permissions:the repo default grants the workflow token.This patch sets
permissions: contents: readat the workflow level so the scope is documented in-file and stays the minimum required byactions/checkout. publish-nightly.yml and publish-release.yml already declare job-level permission blocks (id-token: write for trusted publishing); applying the analogous read-only pattern to ci.yaml closes the gap.No new dependencies, no behavioural change.