Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable GitHub's "Approve and run" button to appear on pull-requests from forks #1109

Merged

Conversation

JakeChampion
Copy link
Owner

@JakeChampion JakeChampion commented Oct 26, 2021

We used a push trigger because that meant we could push the commits that were in the fork into our repo and it would cause the workflow to run on the commits.
That was a good solution when GitHub didn't have a good way to run workflows on forks, but now GitHub has the "Approve and run" (https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks) feature for pull-requests from forks.

Moving to their system means we only need to press a button on the pull-request to run the workflows instead of adding the forked repo as a remote, pulling down their branch with the commits and then pushing those commits to our remote.

@origamiserviceuser origamiserviceuser added this to incoming in Origami ✨ Oct 26, 2021
@github-actions github-actions bot added the library Relates to an Origami library label Oct 26, 2021
@JakeChampion JakeChampion changed the title Enable GitHub's "Approve and run" button to appear on pull-requests f… Enable GitHub's "Approve and run" button to appear on pull-requests from forks Oct 26, 2021
…rom forks

We used a push trigger because that meant we could push the commits that were in the fork into our repo and it would cause the workflow to run on the commits.
That was a good solution when GitHub didn't have a good way to run workflows on forks, but now GitHub has the "Approve and run" (https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks) feature for pull-requests from forks.

Moving to their system means we only need to press a button on the pull-request to run the workflows instead of adding the forked repo as a remote, pulling down their branch with the commits and then pushing those commits to our remote.
@JakeChampion JakeChampion force-pushed the simplify-running-workflows-for-pull-requests-from-forks branch from 8914667 to dad166b Compare October 26, 2021 09:55
@JakeChampion JakeChampion moved this from incoming to ready to review in Origami ✨ Oct 26, 2021
@JakeChampion JakeChampion marked this pull request as ready for review October 26, 2021 11:01
@JakeChampion JakeChampion requested a review from a team as a code owner October 26, 2021 11:01
Copy link
Collaborator

@chee chee left a comment

Choose a reason for hiding this comment

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

jake says this is fine

@JakeChampion JakeChampion enabled auto-merge (rebase) October 26, 2021 13:31
@JakeChampion JakeChampion merged commit 6fb9c97 into master Oct 27, 2021
Origami ✨ automation moved this from ready to review to complete Oct 27, 2021
@JakeChampion JakeChampion deleted the simplify-running-workflows-for-pull-requests-from-forks branch October 27, 2021 12:49
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
@robertboulton robertboulton removed this from Done in Origami ✨ Jul 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
library Relates to an Origami library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants