Many people use version control as a bucket for their stuff. They commit and merge in some shape or form, and it gets shared with their colleagues. Everyone moves on with their lives. Fire & forget sucks when using distributed version control systems.
The trouble with this approach is that it gets complicated to track two simple things:
- When was a change introduced?
- What is the purpose of the change?
How do we use git in a way that makes it easy to track both when a change was introduced, and the intent of the change? Read more »
Recent Comments