People wouldn’t like to see a wrong commit and a revert commit to undo changes of the wrong commit. This pollutes commit history. Here is a simple way for removing the wrong commit instead of undoing changes with a revert commit. git checkout my-pull-request-branch git rebase -i HEAD~n // where n is the number of … Read more
You cannot currently open a pull request on a Gist. You can comment though on the Gist and ask the author to update the Gist from your fork.
Just push more commits on to the branch the request is for. The pull request will pick this up then. Example: If you want to have b merged into master You push c1,c2,c3 to b then you make a new request for b it gets reviewed and you need more commits You push c11,c21,c31 to … Read more
Since the original question / answer, Github has added a new option for this to the restricted branches UI which allows you to set this up. Require pull request reviews before merging When enabled, all commits must be made to a non-protected branch and submitted via a pull request with the required number of approving … Read more
There is a better answer to this problem, though I could just break this down step-by-step. You will need to fetch and checkout the latest upstream changes like so, e.g.: git fetch upstream git checkout upstream/master -b revert/john/foo_and_bar Taking a look at the commit log, you should find something similar to this: commit b76a5f1f5d3b323679e466a1a1d5f93c8828b269 Merge: … Read more
You can just go to GitHub and enter the SHA into the search bar, make sure you select the “Issues” link on the left. UPDATED 13 July 2017 Via the GitHub UI there is a now a really easy way to do this. If you are looking at a commit in the list of commits … Read more
You need to basically create a new branch & cherry-pick the commits you want to add to it. Note: you might need these before the checkout/cherry-pick commands git remote add upstream <git repository> git remote update git checkout -b <new-branch-name> upstream/master git cherry-pick <SHA hash of commit> git push origin <new-branch-name> Afterwards, you will see … Read more
(In addition to the official “GitHub Help ‘Using pull requests’ page”, see also “Forking vs. Branching in GitHub”, “What is the difference between origin and upstream in GitHub”) Couple tips on pull-requests: Assuming that you have first forked a repo, here is what you should do in that fork that you own: create a branch: … Read more
EDIT: After discussing with several OSS maintainers, reviewers is defined as what the word supposed to be: to review (someone’s code) and “assignee” has a looser definiton explained below. For “reviewer”: someone you want to review the code. Not necessarily the person responsible for that area or responsible for merging the commit. Can be someone … Read more
There is no way you can delete a pull request yourself — you and the repo owner (and all users with push access to it) can close it, but it will remain in the log. This is part of the philosophy of not denying/hiding what happened during development. However, if there are critical reasons for … Read more