DEV Community

Discussion on: Avoiding legacy systems

Collapse
 
tkdodo profile image
Dominik D

We have a rule to name branches with issue numbers and a prepare-commit-message script that prepends the branch name, so that every commit can be traced back to it’s origin issue. But the quality of messages really varies πŸ˜…

Collapse
 
dreitzner profile image
Domenik Reitzner

We do the same with branch naming. We also include the issue description in the beach name. We also use gitflow, which helps to keep order. And yes quality of messages really varies πŸ˜€.