Skip to content

Harden CI workflow against untrusted pull requests#665

Draft
jmqd wants to merge 1 commit intomainfrom
jm/ci-security-hardening
Draft

Harden CI workflow against untrusted pull requests#665
jmqd wants to merge 1 commit intomainfrom
jm/ci-security-hardening

Conversation

@jmqd
Copy link
Copy Markdown
Contributor

@jmqd jmqd commented Apr 10, 2026

  • Add ci-approved label check to test-full so external PRs cannot
    run tests with secrets access without maintainer approval.
  • Add approve-ci.yml workflow (pull_request_target) that auto-adds
    the ci-approved label for repo collaborators.
  • Remove unused id-token: write permission from test-full.

@jmqd jmqd force-pushed the jm/ci-security-hardening branch 6 times, most recently from 66a0bdf to 902346e Compare April 10, 2026 14:08
- Add `ci-approved` label check to `test-full` so external PRs cannot
  run tests with secrets access without maintainer approval.
- Add `approve-ci.yml` workflow (`pull_request_target`) that auto-adds
  the `ci-approved` label for repo collaborators.
- Remove unused `id-token: write` permission from `test-full`.
@jmqd jmqd force-pushed the jm/ci-security-hardening branch from 902346e to 6433185 Compare April 10, 2026 14:10
@jmqd jmqd added dependencies Pull requests that update a dependency file ci-approved A label that enables CI to be run on the PR. and removed dependencies Pull requests that update a dependency file labels Apr 10, 2026
@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 78.364% (-0.02%) from 78.38% — jm/ci-security-hardening into main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-approved A label that enables CI to be run on the PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants