It may be useful to have a policy about commit log formats as well. An
example of a commit log with jira ticket number that displays well with git:
TS-#### short summary (50 chars or less), not a sentence
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body. The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.
On 5/17/10 1:29 PM, Leif Hedstrom wrote:
Hi all,
I'd like to open up the discussion on maybe having some "ground rules"
for how we commit, build and test on trunk. I've started a draft on
https://cwiki.apache.org/confluence/display/TS/CommitPolicies
and a few people have already made some modifications to it as well.
Please discuss :).
-- leif
