Y U NO commit??

Re:Y U NO commit?? by lmm on Monday October 20, 2014 @10:24AM (#8482264)

> If you're using Git or another version control that can do squash/rebase, what would be the advantage of having a separate concept of "temporary commits" or something?

It'd be nice to be able to mark commits as "squashable" as I went along (without actually squashing them yet), rather than finishing my feature branch and then have to go back and remember which commits were the "good" ones.

[ Parent | on HN ]

Re:Y U NO commit?? by krupan on Monday October 20, 2014 @10:46AM (#8482357)

As another poster pointed out, Mercurial phases are the answer to this. I don't know if very many mercurial users actually use them this way consciously or not. Most mercurial people that are deliberately and intensely into this workflow learned to use mercurial patch queues before phases existed (patch queues are basically the git staging area on steroids).

[ Parent | on HN ]

Re:Y U NO commit?? by micampe on Monday October 20, 2014 @10:47AM (#8482359)

You can do that with autosquash https://coderwall.com/p/hh-4ea

[ Parent | on HN ]

Re:Y U NO commit?? by lmm on Tuesday October 21, 2014 @08:55AM (#8487036)

Is there an equivalent with a looser match? Half the time I don't remember what my last commit message was.

[ Parent | on HN ]

Re:Y U NO commit?? by micampe on Tuesday October 21, 2014 @01:35PM (#8488525)

No, but this explains a nice trick to use it without remembering the commit message http://technosorcery.net/blog/2012/08/05/updated-git-rebase-...

With that you can do:

    git fixup HEAD~2

[ Parent | on HN ]