| Issue 1071: | Comment renderer doesn't work with standard accepted practice. | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.1
What steps will reproduce the problem?
1. Add a comment with the standard accepted git commit message.
2. Look at renderer
Sample comment:
{quote}
Capitalized, short (50 chars or less) summary
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.
Write your commit message in the present tense: "Fix bug" and not "Fixed
bug." This convention matches up with commit messages generated by
commands like git merge and git revert.
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
- Use a hanging indent
{quote}
What is the expected output? What do you see instead?
I expect the 2nd bullet to look like a bullet in HTML. See the attached pic for what you actually get.
Jul 28, 2011
#1
ericande...@gmail.com
Jul 30, 2011
I at least fully agree in the part that newlines should be outputted as <br /> |
|
| ► Sign in to add a comment |