question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not rendering newlines in commit messages

See original GitHub issue

In the latest v0.6.13, newlines have stopped rendering properly in the body of a commit message, after clicking on a particular commit to view its details.

For example, if the commit message was written like this:

Fix bug in library

- add missing piece of code
- remove incorrect function
- call correct function

It shows up like this in details view:

(Heading)     Fix bug in library
(Subheading)  <author> on <date>

(Body)        - add missing piece of code - remove incorrect function - call correct function

When it should show up like this:

(Heading)     Fix bug in library
(Subheading)  <author> on <date>

(Body)        - add missing piece of code
              - remove incorrect function
              - call correct function

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:9

github_iconTop GitHub Comments

1reaction
rob3ccommented, Nov 19, 2020

@plwalsh Good catch! Blank lines were missing after the title lines - thanks!

1reaction
plwalshcommented, Nov 18, 2020

@rob3c That’s odd; the v0.6.14 update fixed the problem for me.

I wonder if your issue has to do with not leaving a blank line between your first line (“title line”) and the subsequent lines (“full commit message”). See this explanation for the reason why to do this, and this git doc for how git defines the sections.

If you’re seeing the “one single long line” appear above your author name and commit date, that’s what’s happening. This extension renders the title line at the top, followed by the author and commit date, and then lastly the body of the message. You would see a similar one single long line if you ran git log --oneline in a command prompt.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Add line break to 'git commit -m' from the command line
Press ENTER before closing the quotes to add a line break. Repeat as needed. Then close the quotes and hit ENTER twice to...
Read more >
Automatically insert line breaks in git commit messages · Issue ...
I'm trying to get into the habit of writing good commit messages. Not sure if this should be the default but it would...
Read more >
git commit message with line breaks - Reddit
hi there, i want to automate my git commits via bash script. the commit message shall include content from various variables, including some ......
Read more >
GitLab Flavored Markdown (GLFM)
GitLab Flavored Markdown renders GitLab-specific references. For example, you can reference an issue, a commit, a team member, or even an entire project...
Read more >
Writing git commit messages that everybody understands
The rules — not “rules”, but better to follow: · Separate subject from body with blank line · Do not end subject line...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found