git - Setting no "fast forward" as the default when merging. Is this wise and what are some of the consequences? -
so follow workflow of master branch production code only, while development done on development branch merge feature branches. git merge --no-ff
because records commit history of feature branch when merging development. however, i've seen many warnings approach when setting no fast forward default in git config.
has had problems approach? can explain reasons bad idea?
i think 1 downside setting --no-ff default when working team may encounter cases want fast forward merge update feature branch team member collaborated on you.
it might better approach create alias handle merges --no-ff
Comments
Post a Comment