Menu
What is the right workflow for effectively forking a Pull request?
To explain the use case: I've found a repository which contains a pull request that adds a feature I need. Unfortunately the pull request author has gone awol and the repo owner won't accept the pull request until tests are written. I'd like to "fork" the Pull request and write tests so that the repo owner will accept the new functionality.
494
If you don't have access to create branches on that repository, there is no way to create a pull request without forking. Save this answer.
If you have access to a private repository and the owner permits forking, you can fork the repository to your personal account, or an organization on GitHub Team where you have repository creation permissions. You cannot fork a private repository to an organization using GitHub Free.
Forking creates a full copy of your repository, whereas branching only adds a branch to your exiting tree. The file size of branch can vary depending on the branch that you are on. Under the hood git readily accesses the different files and commits depending on what branch you are using.
You can fork the original project, write the unit tests, then use the "Fork Queue" feature to selectively incorporate the changes by the third party into your own repository, and finally issue a pull request to your own repository, unit tests inclusive, to the original repository.
65
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
