version control - Folding git commits -


i think there must commit per feature. however, 1 big feature consists of series of useful pieces. consider refactoring. though, others refactorins side effects of adding/modifying functionality , not deserve separate commit, consider couple of fixes in code. refactor different areas of codebase. not want commit big mess difficult untangle, changes related. therefore spawn more 1 refactoring commit. however, likely, people not want see tiny details. therefore want hide refactoring commits under 1 folder of commits. in history viewer, gitk, should able expand/collapse folder when desired. there solution issue, might solved in other versioning control?

use feature branches. merge them mainline git merge --no-ff. mainline series of merge commits show 1 feature added another, if want see individual commits went feature, they're right there on branch.


Comments

Popular posts from this blog

java - Run a .jar on Heroku -

java - Jtable duplicate Rows -

validation - How to pass paramaters like unix into windows batch file -