Only show commit title in issue history when referencing an issue #1593

New Issue

GiteaMirror · 2025-11-02T04:06:01-06:00

GiteaMirror commented

2025-11-02 04:06:01 -06:00

Originally created by @mbger on GitHub (Mar 5, 2018).

Gitea version (or commit ref): 171914e
Git version:
Operating system:
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes
- No
- Not relevant

Description

I couldn't find an issue which already mentions this but this may have come up before (and it's obviously not a bug).

According to the Git Book it's good practice that commit messages should contain a concise title followed by a more detailed description separated with a blank line:

... As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation.

When following this suggestion, gitea's UI for any referenced issue gets somewhat bloated. I think it may be a good idea to only show the title of the commit message to keep the history timeline more compact. Optionally, there could be an ellipses button (or sth similar) which expands the complete commit message. Below is a screenshot using Tim Pope's commit message template

Screenshots

Originally created by @mbger on GitHub (Mar 5, 2018).  - Gitea version (or commit ref): 171914e - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] [Yes](https://try.gitea.io/mbger/TestRepo/issues/1) - [ ] No - [ ] Not relevant ## Description I couldn't find an issue which already mentions this but this may have come up before (and it's obviously not a bug). According to the [Git Book](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project) it's good practice that commit messages should contain a concise title followed by a more detailed description separated with a blank line: >... As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. When following this suggestion, gitea's UI for any referenced issue gets somewhat bloated. I think it may be a good idea to only show the title of the commit message to keep the history timeline more compact. Optionally, there could be an ellipses button (or sth similar) which expands the complete commit message. Below is a screenshot using [Tim Pope's commit message template](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) ## Screenshots <img width="650" alt="commit-reference" src="https://user-images.githubusercontent.com/5991861/36970411-cafd2dce-2068-11e8-9df9-bdbdfa0c8ab3.png">

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:06:01 -06:00

GiteaMirror closed this issue

2025-11-02 04:06:01 -06:00

GiteaMirror commented

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

@stale[bot] commented on GitHub (Feb 7, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 7, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

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

@adelowo commented on GitHub (Feb 8, 2019):

Unstale

Good bot :)

@adelowo commented on GitHub (Feb 8, 2019): ___Unstale___ > Good bot :)

GiteaMirror commented

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

@mrsdizzie commented on GitHub (Sep 7, 2020):

Duplicate of #12541 (this one came first but the other has more recent activity/likely to get the issue fixed)

@mrsdizzie commented on GitHub (Sep 7, 2020): Duplicate of #12541 (this one came first but the other has more recent activity/likely to get the issue fixed)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1593