Skip to content

Change CI to run on pull_request_target - #333

Open
trond-snekvik wants to merge 1 commit into
mainfrom
fork-ci
Open

Change CI to run on pull_request_target#333
trond-snekvik wants to merge 1 commit into
mainfrom
fork-ci

Conversation

@trond-snekvik

Copy link
Copy Markdown
Collaborator

With the "Require approval for all external contributors" flag set for the repo, and the token permissions being set to content: read and actions: write, I believe this should be perfectly safe for us, and allows fork PRs to run CI - automatically for us and upon approval for external contributors.

With the "Require approval for all external contributors" flag set for the
repo, and the token permissions being set to `content: read` and `actions:
write`, I believe this should be perfectly safe for us, and allows fork PRs
to run CI - automatically for us and upon approval for external
contributors.

Signed-off-by: Trond Snekvik <trond.snekvik@canonical.com>
branches:
- main
pull_request:
pull_request_target:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it is safe to use this trigger for all of the workflows that this kicks off. The build step for untrusted branches should run in an unprivileged job which I think is what pull_request accomplishes. Let's discuss this synchronously to hash through some of the downsides.

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.

2 participants