[WIP] Actions: Enable workflow on fork PR #877
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kyleecodes
changed the title
kyleecodes
changed the title
kyleecodes
changed the title
kyleecodes
changed the title
Enable workflow run on fork PRs by verifying workflow trigger actor permission. New workflow for build-and-test for fork PRs created.
kyleecodes
force-pushed
the
actions/run-tests-from-fork
branch
from
9fa3fb5
to
21089e3
Compare
kyleecodes
changed the title
Merged
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.
Issue link / number:
N/A
What changes did you make?
New workflow
build-and-test-fork-prscreated for fork prs to enable secrets access.Uses
pull_request_targetbut only if the workflow triggering actor is from Chayn.This means
pull_request_targetwill not grant secret access to anyone who makes a pull request.Instead, all public forks triggered by Chayn team members will have access to secrets, even on public forks.
Why did you make the changes?
To save developer time by removing the need to run tests locally for contributor pull requests. With this, devs can conveniently run tests for public pull requests in the UI.