How to handle Pull Requests
Started by markus




10 posts in this topic
markus
Unregistered


 
04-07-2016, 04:38 AM -
#11
Well, I finally figured out why I was having so many problems.

I kept using git pull to get updates from upstream (RPCS3/rpcs3) BUT that just does git fetch and git merge in sequence, and what I really wanted was git fetch and git rebase. Luckily, there is a way to do just that:

Code:
git pull --rebase upstream master

That fetches from upstream (assuming you have defined upstream in git remote) puts it on your master and plays your commits on top of the new updates. This ensures that A) no merge commits and B) your commits are always on top.

I'll edit my OP with this info.


Messages In This Thread
RE: How to handle Pull Requests - by markus - 04-02-2016, 04:48 PM
RE: How to handle Pull Requests - by tambre - 04-02-2016, 05:07 PM
RE: How to handle Pull Requests - by markus - 04-02-2016, 05:36 PM
RE: How to handle Pull Requests - by tambre - 04-02-2016, 05:56 PM
RE: How to handle Pull Requests - by markus - 04-02-2016, 06:02 PM
RE: How to handle Pull Requests - by tambre - 04-02-2016, 06:10 PM
RE: How to handle Pull Requests - by markus - 04-02-2016, 06:48 PM
RE: How to handle Pull Requests - by tambre - 04-02-2016, 06:50 PM
RE: How to handle Pull Requests - by vlj - 04-07-2016, 12:35 AM
RE: How to handle Pull Requests - by tambre - 04-07-2016, 04:02 AM
RE: How to handle Pull Requests - by markus - 04-07-2016, 04:38 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)