Git commit accepts several message flags (-m) to allow multiline commits

Re:Git commit accepts several message flags (-m) to allow mu... by yakshaving_jgt on Wednesday July 08, 2020 @10:22AM (#23770123)

This is me all the time.

[is writing commit message]

Oh wait… What did I change?

  ^Z
  git diff --cached

Oh yeah.

fg

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by gonzus on Wednesday July 08, 2020 @12:22PM (#23771384)

You should be using `git commit -v` then; it will include the full diff of your changes, so you can quickly check them while writing your commit message.

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by seemethere on Wednesday July 08, 2020 @01:35PM (#23772147)

Yeah this is what I use, the only issue being extraordinarily large commits may get bogged down some times.

I have no idea why anyone would ever not use this to be honest.

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by for_xyz on Wednesday July 08, 2020 @12:09PM (#23771249)

That workflow seems really slow when dealing with multiple repos/subrepos actively compared to what UI frontends offer.

But it's still more efficient method for single repository project where using UI git client would be the overkill.

[ Parent | on HN ]