releases/tag page looks broken when no release has been created #10361

New Issue

GiteaMirror · 2025-11-02T09:05:17-06:00

GiteaMirror commented

2025-11-02 09:05:17 -06:00

Originally created by @wiktor-k on GitHub (Mar 1, 2023).

Description

GitHub properly displays release/tag page for tags even if the release has not been created:

Live URL: https://github.com/wiktor-k/pysequoia/releases/tag/v0.1.14

Compare that with the same view of the same object in Gitea:

Live URL: https://try.gitea.io/wiktor/pysequoia/releases/tag/v0.1.14

The title and description are missing and there's a broken markup (%!s(<nil>)) which should default to repository's default branch.

I'd be happy to contribute a fix if this is considered a valid issue.

Thanks for your time!

Gitea Version

1.20.0+dev-48-g04347eb81

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Screenshots attached in the bug description.

Git Version

No response

Operating System

No response

How are you running Gitea?

I'm using try.gitea.io

Database

None

Originally created by @wiktor-k on GitHub (Mar 1, 2023). ### Description GitHub properly displays release/tag page for tags even if the release has not been created: ![2023-03-01-14-55-53](https://user-images.githubusercontent.com/1718963/222161414-efce548b-8796-4568-a09b-633e9e943f16.png) Live URL: https://github.com/wiktor-k/pysequoia/releases/tag/v0.1.14 Compare that with the same view of the same object in Gitea: ![2023-03-01-14-56-09](https://user-images.githubusercontent.com/1718963/222161489-47bec14f-638e-47c8-9572-13b1f20a7423.png) Live URL: https://try.gitea.io/wiktor/pysequoia/releases/tag/v0.1.14 The title and description are missing and there's a broken markup (`%!s(<nil>)`) which should default to repository's default branch. I'd be happy to contribute a fix if this is considered a valid issue. Thanks for your time! ### Gitea Version 1.20.0+dev-48-g04347eb81 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots Screenshots attached in the bug description. ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I'm using try.gitea.io ### Database None

GiteaMirror added the issue/confirmed type/enhancement type/bug labels 2025-11-02 09:05:17 -06:00

GiteaMirror closed this issue

2025-11-02 09:05:18 -06:00

GiteaMirror commented

2025-11-02 09:05:18 -06:00

@silverwind commented on GitHub (Mar 1, 2023):

The title and description are missing and there's a broken markup (%!s()) which should default to repository's default branch.

If by "title and description" you mean the tag message: Yes this would be a very welcome addition. I had requested in the past as well.

The <nil> is definitely a bug.

@silverwind commented on GitHub (Mar 1, 2023): > The title and description are missing and there's a broken markup (%!s(<nil>)) which should default to repository's default branch. If by "title and description" you mean the tag message: Yes this would be a very welcome addition. I had requested in the past as well. The `<nil>` is definitely a bug.

GiteaMirror commented

2025-11-02 09:05:18 -06:00

@wiktor-k commented on GitHub (Mar 27, 2023):

🤔 hmm even though the commit was merged into main it didn't close this issue for some reason. I'll close it manually (as from my PoV it has been completed).

Thank you all for help! I really appreciate it! 🙏

@wiktor-k commented on GitHub (Mar 27, 2023): :thinking: hmm even though the commit was merged into `main` it didn't close this issue for some reason. I'll close it manually (as from my PoV it has been completed). Thank you all for help! I really appreciate it! :pray:

GiteaMirror commented

2025-11-02 09:05:19 -06:00

@silverwind commented on GitHub (Mar 27, 2023):

🤔 hmm even though the commit was merged into main it didn't close this issue for some reason. I'll close it manually (as from my PoV it has been completed).

Thank you all for help! I really appreciate it! 🙏

GitHub's parser is not so smart and did not recognize your "This PR fixes several issues reported in https://github.com/go-gitea/gitea/issues/23221.".

If you put a simple "Fixes: #23221" next time, it will automatically pick it up and close the issue on merge.

@silverwind commented on GitHub (Mar 27, 2023): > 🤔 hmm even though the commit was merged into `main` it didn't close this issue for some reason. I'll close it manually (as from my PoV it has been completed). > > Thank you all for help! I really appreciate it! 🙏 GitHub's parser is not so smart and did not recognize your "This PR fixes several issues reported in https://github.com/go-gitea/gitea/issues/23221.". If you put a simple "Fixes: #23221" next time, it will automatically pick it up and close the issue on merge.

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