git workflow in research environment -


working on academic research still haven't found git workflow our project.

setting: have main project kept in branch master. when new idea emerges new branch created support research. there several parallel researches on main project driven different people.

when working on research branch r (it can take months, , many commits). of commits not directly connected research , improving project itself... want push these commits master branch (they can helpful others).

how should this? cherry-pick? seems me, after lot of cherry-picks (from more people , different branches) difficult merge branch r master @ end.

maybe better option switch master before commit, make commit, switch , pull updates master. seems difficult, 3 reasons:

  1. switch master not easy because many files not committed in conflict etc. (i need use stash somehow)
  2. sometimes realize later, should push older commit(s) r master.
  3. sometimes not want other updates master else. useful later don't have time deal them @ moment.

what proper way of doing it?

you consider:

  • (on branch r) git rebase --interactive: in order reorder commits, 1 want on master first, followed 1 specifics r
  • (on branch master) merge sha1 (the right sha1 of last commit want on master)

but change history of r branch, can issue of others have cloned (you need communicate event, asking them reset r branch new 1 have changed , push).


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -