Hide lastest commit sha when no commit is available #26336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Closed

TheZoker opened this issue Aug 4, 2023 · 0 comments · Fixed by #26340

Labels

TheZoker commented Aug 4, 2023

Description

When I create a new repo without any commit, the Last indexed SHA field looks like this:

Just an empty button. I think the button should be hidden, if the content is not available.

Gitea Version

1.20.2

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Docker compose

Database

SQLite

The text was updated successfully, but these errors were encountered:

TheZoker added the type/bug label

CaiCandong mentioned this issue

Hide last indexed SHA when a repo could not be indexed yet #26340

Merged

delvh closed this as completed in #26340

delvh pushed a commit that referenced this issue


          Hide last indexed SHA when a repo could not be indexed yet (#26340)

9ac6bb0

Now, for a new repo without any commit, the Last indexed SHA field looks like this:
Before:
![image](https://github.com/go-gitea/gitea/assets/50507092/cecc6e24-3366-4093-ae07-c361ea34b373)
After: 
![image](https://github.com/go-gitea/gitea/assets/50507092/9b6ba703-b0d5-4648-ad6b-9a2341dd60f9)

Fixes #26336

GiteaBot mentioned this issue

Hide last indexed SHA when a repo could not be indexed yet (#26340) #26345

Merged

GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue


          Hide last indexed SHA when a repo could not be indexed yet (go-gite…

0bd903d

…a#26340)

Now, for a new repo without any commit, the Last indexed SHA field looks like this:
Before:
![image](https://github.com/go-gitea/gitea/assets/50507092/cecc6e24-3366-4093-ae07-c361ea34b373)
After: 
![image](https://github.com/go-gitea/gitea/assets/50507092/9b6ba703-b0d5-4648-ad6b-9a2341dd60f9)

Fixes go-gitea#26336

wxiaoguang pushed a commit that referenced this issue


          Hide last indexed SHA when a repo could not be indexed yet (#26340) (…

59354d7

…#26345)

Backport #26340 by @CaiCandong

Now, for a new repo without any commit, the Last indexed SHA field looks
like this:
Before:

![image](https://github.com/go-gitea/gitea/assets/50507092/cecc6e24-3366-4093-ae07-c361ea34b373)
After: 

![image](https://github.com/go-gitea/gitea/assets/50507092/9b6ba703-b0d5-4648-ad6b-9a2341dd60f9)


fix #26336

Co-authored-by: CaiCandong <[email protected]>

github-actions bot locked as resolved and limited conversation to collaborators

project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue


          Hide last indexed SHA when a repo could not be indexed yet (go-gite…

f597c78

…a#26340) (go-gitea#26345)

Backport go-gitea#26340 by @CaiCandong

Now, for a new repo without any commit, the Last indexed SHA field looks
like this:
Before:

![image](https://github.com/go-gitea/gitea/assets/50507092/cecc6e24-3366-4093-ae07-c361ea34b373)
After:

![image](https://github.com/go-gitea/gitea/assets/50507092/9b6ba703-b0d5-4648-ad6b-9a2341dd60f9)

fix go-gitea#26336

Co-authored-by: CaiCandong <[email protected]>
(cherry picked from commit 59354d7)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.