Skip to content

Fix last reference to bigrails - #4

Merged
alexevanczuk merged 1 commit into
mainfrom
ae-fix-other-ref-to-bigrails
Jun 14, 2022
Merged

Fix last reference to bigrails#4
alexevanczuk merged 1 commit into
mainfrom
ae-fix-other-ref-to-bigrails

Conversation

@alexevanczuk

@alexevanczuk alexevanczuk commented Jun 14, 2022

Copy link
Copy Markdown
Contributor

No description provided.

@alexevanczuk alexevanczuk changed the title ae fix other ref to bigrails Fix last reference to bigrails Jun 14, 2022
@alexevanczuk
alexevanczuk merged commit 31b3b27 into main Jun 14, 2022
@alexevanczuk
alexevanczuk deleted the ae-fix-other-ref-to-bigrails branch June 14, 2022 19:56
dduugg added a commit that referenced this pull request Aug 17, 2026
Resolves the four open `actions/missing-workflow-permissions` CodeQL
alerts. Each scope is the least privilege the job actually needs:

- build.yml (#5): workflow-level `contents: read`. The single `build`
  job only checks out, restores an `actions/cache` entry, and runs
  `npm ci` / `npm run build:prod` / `npm test`. Neither setup-node nor
  actions/cache needs a token scope beyond reading the repo.
- publish.yml (#1): workflow-level `contents: read`. Despite the name,
  this tag-triggered job does not publish anything — it runs
  `vsce package` and hands the .vsix to `actions/upload-artifact`.
  Uploading an artifact needs no extra scope, there is no
  `vsce publish`, no `gh release create`, and no `npm publish`, so no
  write scope is warranted. The Marketplace release is done off the
  artifact, not by this token.
- stale.yml (#2): job-level `issues: write` + `pull-requests: write`.
  The shared-config stale workflow runs `actions/stale`, which comments
  on and closes both stale issues and stale PRs. A caller's permissions
  are the ceiling for the reusable workflow, so both scopes must be
  granted here or the nightly cron silently stops closing things.
- triage.yml (#4): job-level `issues: write`. The shared-config triage
  workflow only runs `gh issue edit --add-label triage`.

Callers use job-level blocks immediately above `uses:`, matching the
accepted precedent in rubyatscale/query_packwerk. codeql.yml already
declares its permissions and is left 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