git - Merging strategy with a long development branch. How to prevent heavy conflicts in the future merge? -
i'm developing project want make small improvements on master
branch , push them production. have problem because want concurrently work on branch pushed after long time.
if use different branches on long_project
, not merge them immediately, 1 branch ahead. when want launch long_project
branch production, able merge master
without destroying minor work have done on master
?
so, how can merge them after while without destroying minor changes make every day on master
branch?
what is, after making small change on master
, merge master
long project
. way when merge long project
master
, there fewer (if any) conflicts.
Comments
Post a Comment