search for: new_thing_a

...ugh from the switch to compensate for the burden of dealing with these problems. Maybe Gitlab or some other front end would be better. Duncan Murdoch > > 2) Run > git clone giturl.... > to fetch local instance > > 3) Run > git checkout -b feature/new_thing_a > (this is 2. above by Inaki) > > 4) Edit, save, compile, test, revise, ... leading to 1 or more commits > > 5) Run > git push origin > standard configuration should have remote branch follow local branch, I > think the "long form" is...

...re reference; I already followed | Gabor's more complicated instructions and have solved the immediate | problem.) 1) Via GUI: fork or clone at github so that you have URL to use in 2) 2) Run git clone giturl.... to fetch local instance 3) Run git checkout -b feature/new_thing_a (this is 2. above by Inaki) 4) Edit, save, compile, test, revise, ... leading to 1 or more commits 5) Run git push origin standard configuration should have remote branch follow local branch, I think the "long form" is git push --set-upstream origin feature...

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

...burden of dealing with these problems. > > Maybe Gitlab or some other front end would be better. > > Duncan Murdoch > >> >> 2)? Run >> ?????? git clone giturl.... >> ???? to fetch local instance >> ???? 3)? Run >> ?????? git checkout -b feature/new_thing_a >> ???? (this is 2. above by Inaki) >> ???? 4)? Edit, save, compile, test, revise, ... leading to 1 or more commits >> >> 5)? Run >> ?????? git push origin >> ???? standard configuration should have remote branch follow local branch, I >> ???? think the &qu...