Skip to content

Initial commit - #1

Merged
alexevanczuk merged 1 commit into
mainfrom
ae-initial-commit
May 9, 2022
Merged

Initial commit#1
alexevanczuk merged 1 commit into
mainfrom
ae-initial-commit

Conversation

@alexevanczuk

Copy link
Copy Markdown
Contributor

Initial extraction from Gusto codebase

@alexevanczuk
alexevanczuk merged commit edebc5d into main May 9, 2022
@alexevanczuk
alexevanczuk deleted the ae-initial-commit branch May 9, 2022 19:00
dduugg added a commit that referenced this pull request Aug 17, 2026
Resolves the 10 open `actions/missing-workflow-permissions` CodeQL alerts
(#1, #6-#14) by giving every job an explicit least-privilege scope.

ci.yml: one workflow-level `contents: read`. All five jobs (ci-data,
rspec, rspec_ruby_version_file, static_type_check, notify_on_failure)
only check out the repo and run rake/srb, or post to a Slack incoming
webhook — none of them writes anything back to GitHub.

cd.yml: one workflow-level `contents: read` covering check-release
(sparse checkout + a rubygems.org version probe), ci-data
(oxidize-rb/actions/fetch-ci-data), build (checkout, cross-gem,
upload-artifact) and notify_on_release (Slack webhook). The `release`
job keeps its existing job-level `contents: write` override, which it
needs for `gh release create`; job-level permissions replace rather
than intersect the workflow-level block for normal jobs, so the release
path is unaffected.

stale.yml: job-level `issues: write` + `pull-requests: write` on the
shared-config caller. A caller's permissions are the ceiling for the
called workflow, and shared-config's stale.yml runs actions/stale,
which comments on and closes both stale issues and stale PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant