Even if a branch and a commit bundle occupy the same amount of space, in my opinion, commit bundles would appear much cleaner which is the whole point of this anyways.
Thanks On Thursday, January 27, 2022 at 11:30:58 AM UTC+5:30 Tassilo Horn wrote: > Shreyans Jain <[email protected]> writes: > > Hi, > > > So I had an idea if git could have a feature that allows you to squash > > commits into a commit bundle which keeps the commit history clean > > while still maintaining a lot of the important verbose commit > > history. Just wanted some comments on this from the community. > > I think that would create the need for a lot of changes in many places. > But you can achieve what you want with what's there already. Say you > develop a feature on a branch features/feature-x which you push to > origin/features/feature-x. When you are done, you squash the commits on > features/feature-x (but don't push), add a note > > For dev history, see branch features/feature-x. > > to the commit message, and finally merge features/feature-x (not > origin/features/feature-x) into main or wherever it should be. > > Maybe it would be a good convention to rename the branch so that it is > immediately distinguishable from active branches, e.g., to > history/features/feature-x (and then link that in the squash commit's > message). > > Bye, > Tassilo > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/ef050d9b-09ea-400f-bcdb-1cecc59ec4dfn%40googlegroups.com.
