Difference between revisions of "Git Tips Tricks"
Jump to navigation
Jump to search
(add link to old piscisaureus github pr gist) |
|||
| Line 10: | Line 10: | ||
This clones your forked copy of "project" locally, checks out whatever branch the PR is against ("correctbranchname"), then does a combination pull+merge on the upstream project's open PR number 12. | This clones your forked copy of "project" locally, checks out whatever branch the PR is against ("correctbranchname"), then does a combination pull+merge on the upstream project's open PR number 12. | ||
| + | |||
| + | See also, a useful discussion about command line access to pull requests: [https://gist.github.com/piscisaureus/3342247 https://gist.github.com/piscisaureus/3342247]. | ||
Revision as of 17:28, 5 November 2018
Github specific
Github and Pull Requests
Common scenario to run into: you've forked some repo and (or because!) there are outstanding Pull Requests (PRs) created on the upstream project that you want merged into the codebase. This turns out to be relatively easy:
git clone git@github/com:youruser/project.git cd project git checkout correctbranchname git pull https://github.com/upstreamuser/project.git refs/pull/12/head git push origin correctbranchname
This clones your forked copy of "project" locally, checks out whatever branch the PR is against ("correctbranchname"), then does a combination pull+merge on the upstream project's open PR number 12.
See also, a useful discussion about command line access to pull requests: https://gist.github.com/piscisaureus/3342247.