Repo view, no commit refs shown - bug or normal? #981

New Issue

GiteaMirror · 2025-11-02T03:44:15-06:00

GiteaMirror commented

2025-11-02 03:44:15 -06:00

Originally created by @chaosbunker on GitHub (Aug 20, 2017).

Gitea version (or commit ref): 27798c3
Operating system: macOS (git 2.14.0)/Ubuntu (git 2.11)
Database (use [x]):
- [X ] MySQL

Is this what it's supposed to look like? Just links, no commit ref?

this is the view I'm used to from gogs

In the screenshots in the readme, it shows commit refs, that's why I am uncertain.

Originally created by @chaosbunker on GitHub (Aug 20, 2017). - Gitea version (or commit ref): 27798c3 - Operating system: macOS (git 2.14.0)/Ubuntu (git 2.11) - Database (use `[x]`): - [X ] MySQL Is this what it's supposed to look like? Just links, no commit ref? <img width="1139" alt="screen shot 2017-08-20 at 12 07 37" src="https://user-images.githubusercontent.com/16366980/29493920-4661ba7a-85a0-11e7-882b-929be8e4df30.png"> this is the view I'm used to from gogs <img width="997" alt="screen shot 2017-08-20 at 12 06 34" src="https://user-images.githubusercontent.com/16366980/29493929-57b363be-85a0-11e7-95a5-2addfb66c6c3.png"> In the screenshots in the readme, it shows commit refs, that's why I am uncertain.

GiteaMirror added the type/question reviewed/wontfix labels 2025-11-02 03:44:15 -06:00

GiteaMirror closed this issue

2025-11-02 03:44:15 -06:00

GiteaMirror commented

2025-11-02 03:44:16 -06:00

@daviian commented on GitHub (Aug 20, 2017):

It is a desired behaviour, see https://github.com/go-gitea/gitea/issues/1661

@daviian commented on GitHub (Aug 20, 2017): It is a desired behaviour, see https://github.com/go-gitea/gitea/issues/1661

GiteaMirror commented

2025-11-02 03:44:16 -06:00

@chaosbunker commented on GitHub (Aug 20, 2017):

That's too bad, I think it was quite useful to have it visible .. please consider switching back! It wasn't really in the way and for something like this I think information is way more important than design

Sent from my iPhone

On 20. Aug 2017, at 13:23, David Schneiderbauer notifications@github.com wrote:

It is a desired behaviour, see #1661

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@chaosbunker commented on GitHub (Aug 20, 2017): That's too bad, I think it was quite useful to have it visible .. please consider switching back! It wasn't really in the way and for something like this I think information is way more important than design Sent from my iPhone > On 20. Aug 2017, at 13:23, David Schneiderbauer <notifications@github.com> wrote: > > It is a desired behaviour, see #1661 > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. >

GiteaMirror commented

2025-11-02 03:44:16 -06:00

@daviian commented on GitHub (Aug 20, 2017):

@lafriks What's your opinion on this?

@daviian commented on GitHub (Aug 20, 2017): @lafriks What's your opinion on this?

GiteaMirror commented

2025-11-02 03:44:16 -06:00

@tonivj5 commented on GitHub (Aug 20, 2017):

I think it could be optional via a configuration

@tonivj5 commented on GitHub (Aug 20, 2017): I think it could be optional via a configuration

GiteaMirror commented

2025-11-02 03:44:16 -06:00

@lafriks commented on GitHub (Aug 20, 2017):

There is not much use in it as you are not able to easy copy it anyway as it is link and it takes a lot space in file list. Also I don't think looking at hash really means anything to you at least in file list. If you need commits hash from file list you can still get it from commits message url and it will be much easier than copying from UI as it was previously. Other reason is that no other git web ui shows hashes in code file listing

@lafriks commented on GitHub (Aug 20, 2017): There is not much use in it as you are not able to easy copy it anyway as it is link and it takes a lot space in file list. Also I don't think looking at hash really means anything to you at least in file list. If you need commits hash from file list you can still get it from commits message url and it will be much easier than copying from UI as it was previously. Other reason is that no other git web ui shows hashes in code file listing

GiteaMirror referenced this issue

2025-11-02 11:52:30 -06:00

[PR #981] [MERGED] Security: fix XSS attack on alert #15695

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#981