Skip to content

feat(e2e): authorize fork comment checks - #271

Draft
vcauesantos wants to merge 4 commits into
mainfrom
devops-1541/allow-fork-e2e-commands
Draft

vcauesantos wants to merge 4 commits into
mainfrom
devops-1541/allow-fork-e2e-commands

Conversation

@vcauesantos

@vcauesantos vcauesantos commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add opt-in fork support to comment-triggered-check
  • require write, maintain, or admin permission before a commenter can approve fork code
  • add a queue/resolve handoff for a native pull_request workflow
  • keep fork support disabled by default

Security

The privileged issue_comment workflow never checks out fork code. For an approved fork request, it records the parsed command and toggles an internal label with a GitHub App or PAT token. A pull_request: labeled workflow accepts only the trusted bot's request for the pull request's exact head SHA.

This preserves the normal pull request cache scope and avoids dispatching the base branch before checking out fork code.

Testing

  • make test-comment-triggered-check (188 passed)
  • shellcheck -x .github/actions/comment-triggered-check/src/*.sh
  • make check-docs

Part of DEVOPS-1541.

After merge, comment-triggered-check/v1 must be advanced before the caller PRs can merge.

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