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

Switch to pull_request_target strategy #608

Merged
merged 1 commit into from
Oct 31, 2023
Merged

Switch to pull_request_target strategy #608

merged 1 commit into from
Oct 31, 2023

Conversation

zkoppert
Copy link
Member

@zkoppert zkoppert commented Oct 31, 2023

fixes #581

This changes from running the gitbook workflow on the upstream repo to actually running it on the fork that a contributor has created with a changeset. The hope is that this will address the failing builds described in #581 . In order to test this change I believe we need to merge this through to the main branch and then open a pull request from a fork which would trigger this github action job.

cc/ @spier

@spier spier merged commit 94481b0 into InnerSourceCommons:main Oct 31, 2023
2 checks passed
@spier
Copy link
Member

spier commented Oct 31, 2023

Thank you @zkoppert. This PR is merged.

Could you also create PR from your fork, to test if this works?
I am worried that if I test this from my own fork, my elevated permissions on the upstream may create misleading results.

@spier
Copy link
Member

spier commented Oct 31, 2023

I forgot that I can push changes to a PR submitted from a fork myself.
And through that test the pull_request_target from a fork.

Just did that. However it looks like the workflow is still failing. See:
https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/579/checks

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.

Unexpected failure in GitHub Action run
2 participants