Skip to content

Restrict GITHUB_TOKEN permissions in CI workflow#38

Merged
dduugg merged 1 commit into
mainfrom
fix-ci-workflow-permissions
Jul 24, 2026
Merged

Restrict GITHUB_TOKEN permissions in CI workflow#38
dduugg merged 1 commit into
mainfrom
fix-ci-workflow-permissions

Conversation

@dduugg

@dduugg dduugg commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Resolves code scanning alert #2 (actions/missing-workflow-permissions): the call-workflow-from-shared-config job in ci.yml had no explicit permissions block, so it defaulted to the repository's token permissions.
  • Added permissions: contents: read on the job. The called reusable workflow (rubyatscale/shared-config/.github/workflows/ci.yml) only checks out code (with persist-credentials: false) and posts failure notifications via a Slack webhook secret — neither needs write access to GITHUB_TOKEN.

Test plan

  • Confirm the CI workflow still passes (tests, type check, lint) after merge
  • Confirm code scanning alert Docs and cleanups #2 is auto-resolved on the next CodeQL run against main

Resolves CodeQL alert actions/missing-workflow-permissions: the
shared-config CI workflow only checks out code (with
persist-credentials: false) and posts to a Slack webhook, neither of
which needs write access, so contents: read is sufficient.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant