Message232102
+The workflow of a developer might look something like this:
"a core developer" or "a contributor"? It would be good to split core developer and contributor workflows.
+ # address review comments and merge
+ git checkout master
+ git merge issueA
+ git branch -d issueA
For example, from the contributor side, you shouldn't touch the master branch at all.
It should be:
# address review comments
git commit -a
# check upstream and rebase
git pull --rebase upstream master # or "origin master" in this example
# push changes (optional)
git push origin issueA # origin should be contributor's fork here |
|
Date |
User |
Action |
Args |
2014-12-04 03:56:25 | berker.peksag | set | recipients:
+ berker.peksag, ezio.melotti, demian.brecht |
2014-12-04 03:56:25 | berker.peksag | set | messageid: <1417665385.22.0.423071821516.issue22992@psf.upfronthosting.co.za> |
2014-12-04 03:56:25 | berker.peksag | link | issue22992 messages |
2014-12-04 03:56:24 | berker.peksag | create | |
|