Displaying 3 results from an estimated 3 matches for "upstreammaster".
2018 Jan 25
4
Why R should never move to git
...he upstream repo as another remote:
>
> git remote add upstream https://github.com/the/original/repo
>
> 2) Pull the upstream master with a different name:
>
> git pull upstream master:patch2
I've done all that, and now on my local copy I have a branch. I called
it "upstreamMaster", because at this point it matches the upstream
master, and I intend to maintain it that way.
>
> 3) Edit, add, commit and push patch2 to your fork:
>
> git checkout patch2
> ...
> git push origin patch2
I did this, except that the "..." contains nothing, becau...
2018 Jan 25
0
Why R should never move to git
...;
>> git remote add upstream https://github.com/the/original/repo
>>
>> 2) Pull the upstream master with a different name:
>>
>> git pull upstream master:patch2
>>
>
> I've done all that, and now on my local copy I have a branch. I called it
> "upstreamMaster", because at this point it matches the upstream master, and
> I intend to maintain it that way.
>
>
>> 3) Edit, add, commit and push patch2 to your fork:
>>
>> git checkout patch2
>> ...
>> git push origin patch2
>>
>
> I did this, except that...
2018 Jan 25
4
Why R should never move to git
On 25/01/2018 2:57 AM, I?aki ?car wrote:
> For what it's worth, this is my workflow:
>
> 1. Get a fork.
> 2. From the master branch, create a new branch called fix-[something].
> 3. Put together the stuff there, commit, push and open a PR.
> 4. Checkout master and repeat from 2 to submit another patch.
>
> Sometimes, I forget the step of creating the new branch and I