ci: run fork pull requests via pull_request_target behind a review gate - #1032
Merged
Conversation
Signed-off-by: Leonardo Carreras <leonardo.carreras@eonerc.rwth-aachen.de>
leonardocarreras
temporarily deployed
to
internal
July 29, 2026 23:23 — with
GitHub Actions
Inactive
stv0g
approved these changes
Jul 30, 2026
Contributor
|
Unfortunately #1020 still seems to fail? |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fork PRs like #1020 fail from
prepareonward, because fork runs get a read-onlyGITHUB_TOKENand cannot push to ghcr.Forks can now run via
pull_request_target, which is safe because each run needs approval from a member. Nothing changes for same-repo PRs. Tags are unchanged.Needs the env
fork-prto be created with required reviewers before merge. Sorry @stv0g, I will need to make you work a bit extra because this needs admin rights.