conflicts in Git feature branches, how to detect them early -


with developing java git, have frequent problem different people change same classes in different feature branches, results in merge conflicts. while these problems inevitable point, detect these problems early, people can talk , align.

i see 2 possible solutions here: best practices (like looking @ other peoples branches) , tool support. if miss best practices, please point me document. if there tools (you add branches list , email in case of possible conflicts), please tell me.

that's similar continuous integration.

you have whatever build-system use continuous integration (teamcity, jenkins) try merge branches every day/hour , send e-mail when failed automatically.


Comments

Popular posts from this blog

sublimetext3 - what keyboard shortcut is to comment/uncomment for this script tag in sublime -

java - No use of nillable="0" in SOAP Webservice -

ubuntu - Laravel 5.2 quickstart guide gives Not Found Error -