Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to fast track branch after pull request in Github

Tags:

git

github

Not sure if this is the place to ask questions about Github.

I have forked a public repo and added two commits to it, then sent to the original author asking for a pull request. The author have complied with the request and now I'd wish to fast track my own repo to the HEAD of the author's repo. All of my new commits are in the author's repo now, so there aren't any side-tracked commits (what's the proper name for this btw? I thought it was fork but that sounded weird considering how Github refer to forks.).

Thanks!

like image 282
gtr32x Avatar asked Mar 07 '12 02:03

gtr32x


People also ask

What should I do with branch after pull request?

After receiving the pull request, the project maintainer has to decide what to do. If the feature is ready to go, they can simply merge it into main and close the pull request. But, if there are problems with the proposed changes, they can post feedback in the pull request.

How do I sync my GitHub branch?

In GitHub Desktop, click Current Branch. Click Choose a branch to merge into BRANCH. Click the branch you want to merge into the current branch, then click Merge BRANCH into BRANCH. Note: If there are merge conflicts, GitHub Desktop will warn you above the Merge BRANCH into BRANCH button.

How do I merge Pull Requests and branches?

Under your repository name, click Pull requests. In the "Pull Requests" list, click the pull request you'd like to merge. Depending on the merge options enabled for your repository, you can: Merge all of the commits into the base branch by clicking Merge pull request.

How do you fix this branch is out of date with the base branch?

Update your pull request branch by rebasing When your pull request's branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch.


1 Answers

As described in the GitHub help page for fork, the best policy here is to:

  • define a remote called upstream and pointing to the original repo (the one where the author accepted your pull request)
  • pull from that upstream repo

Pull in upstream changes

If the original repo you forked your project from gets updated, you can add those updates to your fork by running the following code:

$ git fetch upstream
$ git merge upstream/master

Or you could, after the fetch, reset your master branch to upstream/master, in order to have the exact same history.

So, when you fork a repo, and clone that forked repo to your workstation:

  • remote 'origin' refers to your fork
  • remote 'upstream' refers to the original repo that your forked. You need to explicitly add that remote reference to your repo.
like image 88
VonC Avatar answered Sep 23 '22 18:09

VonC