-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cannot create PR here from my gitflow-avh fork #7
Comments
Thank you for bringing this to my attention. I'll look into this and get it resolved and let you know. |
gitflow-cjs is now setup as a direct fork of gitflow-avh. I was able to select my fork from the base repository drop down menu when I selected new pull request from your fork Since my fork of gitflow is not your upstream you would need to do this every time you wanted to submit a PR from the webUI. There's a ongoing discussion Change default base repository for pull requests on forks That deals with a similar situation. In short right now the only way to change the default base repository for PR's would be to create a new fork if using the webUI for PR's. |
That worked, and I was even able to do it with the webUI. (No manual URL editing.) |
Summary: Please find an easy way to allow easy submission/migration of PRs from petervanderdoes/gitflow-avh to your repo.
I saw your request:
And I see that you made the same request on other open PRs there.
However, I can't create a PR on this repo from my gitflow-avh fork.
I could create a PR on your other repo (CJ-Systems/gitflow-avh, which was forked from petervanderdoes/gitflow-avh), but I had to manually edit the URL to start it. (GitHub was trying to make me do the PR from my branch on its upstream (petervanderdoes/gitflow-avh), and would not allow even your gitflow-avh fork in the pull-down menu (let alone your gitflow-cjs).)
When I try to do the same manual URL modification to create the PR on this repo (gitflow-cjs), it doesn't even let me.
If you want people to migrate their PRs from petervanderdoes/gitflow-avh to here, you'll probably get the most compliance if you make it as easy as possible for them to do so. I think you'll need to start by making your target repo a proper fork of petervanderdoes/gitflow-avh. Then it seems you may need to also provide instructions on how to create the PRs (which may include manually tweaking the URL, since GitHub doesn't seem to make it possible to submit a PR to a peer repo using the webUI).
The text was updated successfully, but these errors were encountered: