Skip to content

Initial commit - #5

Merged
alexevanczuk merged 1 commit into
mainfrom
ae-initial-commit
Dec 21, 2022
Merged

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

Conversation

@alexevanczuk

Copy link
Copy Markdown
Contributor

No description provided.

@alexevanczuk
alexevanczuk merged commit b4983b1 into main Dec 21, 2022
@alexevanczuk
alexevanczuk deleted the ae-initial-commit branch December 21, 2022 13:38
dduugg added a commit that referenced this pull request Aug 17, 2026
Resolves the six open `actions/missing-workflow-permissions` CodeQL alerts
(#1, #2, #4, #5, #6, #7) by giving every job an explicit, least-privilege
permissions block.

- ci.yml: one workflow-level `contents: read`. All three jobs (rspec,
  static_type_check, notify_on_failure) only check out the repo and run
  rspec / srb tc; the Slack notifier posts to an incoming webhook and needs
  no GitHub API scope at all, so read is the floor that covers the file.
- cd.yml: `contents: write` on the caller job. shared-config's cd.yml runs
  discourse/publish-rubygems-action, which does a raw `git push` of the
  release tag, and then `gh release create` — both need write. Caller
  permissions are the ceiling for a reusable workflow, so anything less
  would break releases.
- stale.yml: `issues: write` + `pull-requests: write`. shared-config's
  stale.yml runs actions/stale, which comments on and closes both stale
  issues and stale PRs.
- triage.yml: `issues: write`. shared-config's triage.yml runs
  `gh issue edit --add-label triage` (its own job already declares
  `issues: write`; the caller must grant at least that).

codeql.yml already declares its permissions and is untouched.
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