I really like the idea of a function-based workflow in Git: using function branches to support concurrent development.
In a functional process based on functions, I would develop my tasks into function branches (from the wizard), and I would often refuse the owner to avoid potential conflicts. If you work together, I push / pull the function branch to the remote. When you are ready to integrate into master, I open a request to transfer from my function branch to master, so that load requests are viewed by peers and are automatically evaluated to find out if the pull request (merging my function with a branch in master) is assembly and block- tests. If the retrieval request is green, my function branch is automatically merged for control.
I found that the above workflow is perfect. However, in some Internet communications, they advocate “backbone-based development” (for example, 1 , 2 ).
As far as I understand, development based on highways does not encourage the development of individual function branches, but all developers develop into wizards. This model encourages developers to integrate daily (Martin Fowler CI practice) to the wizard to avoid conflicts (unlike what I would do, reinstall my function branch to master).
I was wondering what advantages this model will bear on the basis of the model. I have a few doubts about the external line model:
? : . , , ? , , , ( )?
? , . , (-). ?
, "", - , . , , , ?
- , ?
: -)