Release URL redirected to project page #3544

New Issue

GiteaMirror · 2025-11-02T05:16:35-06:00

GiteaMirror commented

2025-11-02 05:16:35 -06:00

Originally created by @pditommaso on GitHub (Jul 8, 2019).

When creating a new release the URL provided redirected to the project page instead of the release-specific page.

For example, in the release page I've created a foo release. The foo release link is

https://try.gitea.io/pditommaso/stress/src/tag/foo

When opening the link it shows the project page.

Tested on http://try.gitea.io

Originally created by @pditommaso on GitHub (Jul 8, 2019). When creating a new release the URL provided redirected to the project page instead of the release-specific page. For example, in the [release page](https://try.gitea.io/pditommaso/stress/releases) I've created a `foo` release. The `foo` release link is https://try.gitea.io/pditommaso/stress/src/tag/foo When opening the link it shows the project page. <img width="1272" alt="Screenshot 2019-07-08 at 15 14 21" src="https://user-images.githubusercontent.com/816968/60813045-21275100-a193-11e9-8a71-ff05affc61a0.png"> Tested on http://try.gitea.io

GiteaMirror added the type/question issue/stale labels 2025-11-02 05:16:35 -06:00

GiteaMirror closed this issue

2025-11-02 05:16:35 -06:00

GiteaMirror commented

2025-11-02 05:16:36 -06:00

@pditommaso commented on GitHub (Jul 8, 2019):

OK, I think I've figured out what the problem. I was expecting the link in the release page would open a specific page for that release. The link provided is the project repo for that tag, which is really confusing.

Also, it's not clear how to access a specific release page (for example to download associated assets) when the release page contains many releases.

@pditommaso commented on GitHub (Jul 8, 2019): OK, I think I've figured out what the problem. I was expecting the link in the release page would open a specific page for that release. The link provided is the project repo for that tag, which is really confusing. Also, it's not clear how to access a specific release page (for example to download associated assets) when the release page contains many releases.

GiteaMirror commented

2025-11-02 05:16:36 -06:00

@stale[bot] commented on GitHub (Sep 6, 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 (Sep 6, 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 05:16:36 -06:00

@stale[bot] commented on GitHub (Sep 20, 2019):

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

@stale[bot] commented on GitHub (Sep 20, 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:23:38 -06:00

[PR #3544] [MERGED] Added checks for protected branches in pull requests #16987

GiteaMirror referenced this issue

2025-11-02 12:24:57 -06:00

[PR #3689] [MERGED] Add protected branch whitelists for merging #17043

Sign in to join this conversation.