Skip to content

Support to open pull request to another repo #70

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

Merged
merged 9 commits into from
Apr 27, 2021
Merged

Conversation

mszhanyi
Copy link
Contributor

I need to submit PRs to another PR but GITHUB_REPOSITORY always refers to current repo.
So I make this little change, maybe others need this option as well

@vsoch
Copy link
Owner

vsoch commented Apr 19, 2021

Thanks @mszhanyi that's an interesting idea! I should be able to take a look over the weekend.

@@ -71,6 +73,8 @@ an issue or PR, they are ignored otherwise.
The `GITHUB_TOKEN` secret is required to interact and authenticate with the GitHub API to open
the pull request. The example is [deployed here](https://github.com/vsoch/pull-request-action-example) with an example opened (and merged) [pull request here](https://github.com/vsoch/pull-request-action-example/pull/1) if needed.
Copy link
Owner

Choose a reason for hiding this comment

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

@mszhanyi I'm wondering if there is a way to make this less complicated. E.g., the user still could use the GITHUB_TOKEN variable defined in secrets to be a PAT? Are there cases when both would be wanted so this wouldn't work?

And the same question for GITHUB_REPOSITORY. Is there a way to not have two variables for the "same" thing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

update with comments

Co-authored-by: Vanessasaurus <[email protected]>
@vsoch vsoch merged commit 1cb1956 into vsoch:master Apr 27, 2021
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