Gitea: Repo view, no commit refs shown - bug or normal?

Created on 20 Aug 2017  Â·  5Comments  Â·  Source: go-gitea/gitea

  • 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?
screen shot 2017-08-20 at 12 07 37

this is the view I'm used to from gogs
screen shot 2017-08-20 at 12 06 34

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

kinquestion reviewewontfix

All 5 comments

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

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.

@lafriks What's your opinion on this?

I think it could be optional via a configuration

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

haytona picture haytona  Â·  3Comments

Fastidious picture Fastidious  Â·  3Comments

tuxfanou picture tuxfanou  Â·  3Comments

mirhec picture mirhec  Â·  3Comments

flozz picture flozz  Â·  3Comments