Merging / forking

Is there any good online resource that describes different practices for merging / forking, regardless of version control tool?

This should apply to the version of the clients, the development of functions, bug fixes, etc.

+4
source share
2 answers

Good link (which I mention in the When you Should Insert section):

Chapter 7 “How Software Develops” (pdf)

From Practical Performance (Laura WINGERD - O'Reilly): This is a good introduction (VCS agnostic) for combining workflow between different types of branches.

+3
source

Very good question. I had the same interest in how best to use git. So far, the best working solution that we use is to fix errors in the "patch" branches from the oldest supported version, and then merge them into later and finally "leading" branches. For new functions, create them on separate branches, combining the "master" in the function branches to update them, and when the time has come to release this function, merge the "feature" branch into "master".

+1
source

All Articles