Gitea website does not properly display newlines in commit messages #1827

New Issue

GiteaMirror · 2025-11-02T04:14:27-06:00

GiteaMirror commented

2025-11-02 04:14:27 -06:00

Originally created by @LouieK22 on GitHub (May 27, 2018).

Gitea version (or commit ref):
Git version: 773530c
Operating system: Docker on Ubuntu 16.04
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL) https://try.gitea.io/LouieK22/newline-test
- No
- Not relevant

Description

When a commit message contains a newline it is not displayed on the Gitea website.
...

Screenshots

The screenshots should have another line that read "WIP and Disabled"

Originally created by @LouieK22 on GitHub (May 27, 2018).  - Gitea version (or commit ref): - Git version: 773530c - Operating system: Docker on Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://try.gitea.io/LouieK22/newline-test - [ ] No - [ ] Not relevant ## Description When a commit message contains a newline it is not displayed on the Gitea website. ... ## Screenshots ![](https://i.imgur.com/OjMcEO3.png) ![](https://i.imgur.com/zxkR4ih.png) The screenshots should have another line that read "WIP and Disabled"

GiteaMirror added the type/bug label 2025-11-02 04:14:28 -06:00

GiteaMirror closed this issue

2025-11-02 04:14:28 -06:00

GiteaMirror commented

2025-11-02 04:14:29 -06:00

@lafriks commented on GitHub (May 28, 2018):

Can you reproduce that on try.gitea.io?

@lafriks commented on GitHub (May 28, 2018): Can you reproduce that on try.gitea.io?

GiteaMirror commented

2025-11-02 04:14:29 -06:00

@LouieK22 commented on GitHub (May 28, 2018):

Yes

@LouieK22 commented on GitHub (May 28, 2018): Yes ![](https://i.imgur.com/aPAeEzZ.png)

GiteaMirror commented

2025-11-02 04:14:29 -06:00

@lunny commented on GitHub (May 28, 2018):

It's some critical, so I moved it to v1.5.0 and added backport

@lunny commented on GitHub (May 28, 2018): It's some critical, so I moved it to v1.5.0 and added backport

GiteaMirror commented

2025-11-02 04:14:29 -06:00

@sondr3 commented on GitHub (May 30, 2018):

This might be related to my expandable commit bodies PR, are the lines separated by a \n or something else? Cause I forgot that Windows for example does new lines differently than Linux, so it might be a editor issue.

On second though, this is likely related to the above but more because you didn’t split the lines apart by a double new line. I’m in the middle of my exams so I won’t be able to test myself for a week or so, but if it still is an issue I’ll take a look.

@sondr3 commented on GitHub (May 30, 2018): This might be related to my expandable commit bodies PR, are the lines separated by a `\n` or something else? Cause I forgot that Windows for example does new lines differently than Linux, so it might be a editor issue. On second though, this is likely related to the above but more because you didn’t split the lines apart by a double new line. I’m in the middle of my exams so I won’t be able to test myself for a week or so, but if it still is an issue I’ll take a look.

GiteaMirror referenced this issue

2025-11-02 12:03:14 -06:00

[PR #1954] [CLOSED] Add wrapping to long diff lines to fix #1827 #16141

GiteaMirror referenced this issue

2025-11-02 12:14:16 -06:00

[PR #2789] [MERGED] Add wrapping to long diff lines #16595

Sign in to join this conversation.