ci: declare contents: read for the bazel test workflow#636
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
The single job in this workflow checks out the repo and runs bazel test with remote cache via Google service-account credentials (passed as the GOOGLE_CREDENTIALS secret). It does not write to the repo or call GitHub APIs for any write, so contents: read is the minimum GITHUB_TOKEN scope it needs. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
931f522 to
2484983
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
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.
Tiny hardening change. The single
bazel_testjob in.github/workflows/bazel-test.yamlonly checks out the repo and runsbazel testwith remote cache via Google service-account credentials (passed as theGOOGLE_CREDENTIALSsecret). It does not write to the repo or call GitHub APIs for any write, so the workflow'sGITHUB_TOKENonly needscontents: read.YAML parses cleanly (
python -c 'import yaml; yaml.safe_load(...)').