git - What is a more efficient and collaborate way of merging branches that has too many commits? -


we medium level organization around 40 developers. have multiple branches different releases simultaneous development.

the problem face when merge release-branch on master is, there 2 many commits involved , overwhelming understand changes went in , developer merging branches unable decide chunks let in , not. auto-merged files catching lots of wrong merges.

how big companies go doing these merges in more efficient , collaborative way? popular git workflows aware of? create new merged branch , ask developers check/comment if merge happened , merge master?

please advice

i suggest @ pull requests.

they way @ has changed 1 branch and, because can add many approvers wish, many developers can review , comment wherever want, creating discussion changes merged.

in experience, used on atlassian stash , nice collaborate on merge. suggest @ this documentation atlassian, part "discussing pull request".

pull requests used lot on github, merge contribution fork initial repository. more information github pull requests can found here.


Comments

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -