commit-message

I read once that git commit messages should be in the imperative present tense, e.g. "Add tests for x". I always find myself using the past tense, e.g. "Added tests for x" though, which feels a lot more natural to me. Here's a recent John Resig commit showing the two in one message: Tweak some more jQuery set results in the manipulation tests. Also fixed the order of the expected test results. Does it matter? Which should I use? mipadi The preference for present-tense, imperative-style commit messages comes from Git itself. From Documentation/SubmittingPatches in the Git repo: Describe your

I'm using Visual SVN Server and Tortoise SVN (client) for source control. I would like all developers to standardize on a consistent format for checkin notes. For Example I want their Commit Message to default to... Synopsis: Developer Name: (pre-populated) Reviewed By: [Bug Id]: [Change Bug State]: Known Issues: Affected Files: (pre-populated) In the future I'd like [Bug Id] and [Bug State] to supply the information to trigger an automated update to the Bug Tracking system. Also Developer Name and Affected Files should be prepopulated with the svn user and files that the user is commiting.

This question already has an answer here: How to amend a commit without changing commit message (reusing the previous one)? 5 answers I'm running a very rapid code-compile-test loop where I am amending changes to my commits far more often than not. For example: # Make some changes $ git commit -m "Added feature X" # Compile, test # Fix bugs $ git commit -a --amend I usually want the same commit message after I fix my bugs. Is there a way to make git skip firing up my EDITOR and just use the original commit message? You can just add --no-edit to use the last message. This option existed since

This question already has an answer here: Mercurial: how to amend the last commit? 7 answers I am currently using TortoiseHg (Mercurial) and accidentally committed an incorrect commit message. How do I go about editing this commit message in the repository? Thilo Update: Mercurial has added --amend which should be the preferred option now . You can rollback the last commit (but only the last one) with hg rollback and then reapply it. Important : this permanently removes the latest commit (or pull). So if you've done a hg update that commit is no longer in your working directory then it's gone

I need a plumbing command to print the commit message of one given commit - nothing more, nothing less. It's not "plumbing", but it'll do exactly what you want: $ git log --format=%B -n 1 <commit> If you absolutely need a "plumbing" command (not sure why that's a requirement), you can use rev-list : $ git rev-list --format=%B --max-count=1 <commit> Although rev-list will also print out the commit sha (on the first line) in addition to the commit message. git show is more a plumbing command than git log , and has the same formatting options: git show -s --format=%B SHA1 Harshniket Seta This