Skip to content

Instantly share code, notes, and snippets.

@prakash-gamit
Last active August 29, 2015 14:12
Show Gist options
  • Save prakash-gamit/b44910b89af004583c25 to your computer and use it in GitHub Desktop.
Save prakash-gamit/b44910b89af004583c25 to your computer and use it in GitHub Desktop.
Short (50 chars or less) summary of changes
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.
Further paragraphs come after blank lines.
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet,
preceded by a single space, with blank lines in
between, but conventions vary here
--
originally written by _Tim Pope_
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment