3 ms·
Define "useful history". ;) There's history in the sense of "log of everything that happened" but also in the sense of a nice record of decisions that were mad
by andrewflnr 14y ago
Define "useful history". ;)
There's history in the sense of "log of everything that happened" but also in the sense of a nice record of decisions that were made, documentation essentially. I'm guessing "no feature branches" aims more for the latter. Personally, I'm not sure why we shouldn't have both.
- SoftwareMaven 14y agoBoth would be nice. I generally restructure commits before pushing them to master in order to make them easier to read, which is nice for others. However, I think about the code in the order I built it, especially when I need to remember why I did something. Unfortunately, that information gets lost if I forget. On the whole, I think restructuring is good (I haven't always felt this way), but something is lost in the process.
- turtlepower 14y agoIn this case I'd like to be able to revert the merge.
- sanderjd 14y agoFeature branches, merge commits, and small (possibly broken!) commits are all better documentation of the process of developing a feature than big "cleaned up" commits.