Change Details

"and an empty message aborts the commit", says the comment in the git commit template. Except that in the private repo, our hook doesn't check for this, and helpfully adds in $SUDO_USER, and so by the time git sees it again the commit message is decidedly non-empty. This isn't //too// big a deal, but has bit myself and @akosiaris in the past few weeks.

The comment in the git commit template says "and an empty message aborts the commit". Except that in the private repo, our hook doesn't check for this, and helpfully adds in $SUDO_USER, and so by the time git sees it again the commit message is decidedly non-empty. This isn't //too// big a deal, but has bit myself and @akosiaris in the past few weeks.

"and an empty message aborts the commit",The comment in the git commit template says the comment in the git commit template"and an empty message aborts the commit". Except that in the private repo, our hook doesn't check for this, and helpfully adds in $SUDO_USER, and so by the time git sees it again the commit message is decidedly non-empty. This isn't //too// big a deal, but has bit myself and @akosiaris in the past few weeks.