UX: Commit status not visible in presence of long log summary #2977

New Issue

GiteaMirror · 2025-11-02T04:55:53-06:00

GiteaMirror commented

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

Originally created by @strk on GitHub (Feb 26, 2019).

As of Gitea 1.5.2 commit statuses for commits having a summary log longer than a given number of characters are truncated with the final part replaced by .... In these cases the commit status icon related to CI reporting (Drone) isn't shown (is truncated, I guess).

Note that the commit page itself does NOT report the status either so there's no way to tell the status of the commit. Pretty annoying.

I did not try on try.gitea.io

Originally created by @strk on GitHub (Feb 26, 2019). As of Gitea 1.5.2 commit statuses for commits having a summary log longer than a given number of characters are truncated with the final part replaced by `...`. In these cases the commit status icon related to CI reporting (Drone) isn't shown (is truncated, I guess). Note that the commit page itself does NOT report the status either so there's no way to tell the status of the commit. Pretty annoying. I did not try on try.gitea.io

GiteaMirror added the topic/ui issue/stale type/bug labels 2025-11-02 04:55:53 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

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

@strk commented on GitHub (Feb 26, 2019):

Here's where you can see the problem: https://git.osgeo.org/gitea/geos/geos/pulls/74#issuecomment-3845

@strk commented on GitHub (Feb 26, 2019): Here's where you can see the problem: https://git.osgeo.org/gitea/geos/geos/pulls/74#issuecomment-3845

GiteaMirror commented

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

@techknowlogick commented on GitHub (Feb 26, 2019):

@strk as I'm a bit jetlagged I just want to ensure that I am understanding everything correctly, I apologize. You mean how on the commits tab of that PR, one of the commits doesn't have a status due to the commit message being too long (but the second commit does)? (I've attached a screenshot of the part I mean)

@techknowlogick commented on GitHub (Feb 26, 2019): @strk as I'm a bit jetlagged I just want to ensure that I am understanding everything correctly, I apologize. You mean how on the commits tab of that PR, one of the commits doesn't have a status due to the commit message being too long (but the second commit does)? (I've attached a screenshot of the part I mean) ![screen shot 2019-02-26 at 10 38 54 am](https://user-images.githubusercontent.com/164197/53425333-c8f56c80-39b2-11e9-8ae7-95d674cf7d95.png)

GiteaMirror commented

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

@stale[bot] commented on GitHub (Apr 28, 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 (Apr 28, 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:55:54 -06:00

@stale[bot] commented on GitHub (May 12, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 12, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

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

[PR #2977] [MERGED] Fix fault PR renaming app.ini (#1522) #16691

Sign in to join this conversation.