Compare-Button leads to 404 #353

Closed
opened 2025-11-02 03:19:53 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @evilstiefel on GitHub (Feb 14, 2017).

Description

When creating a repository, next to the branch-dropdown, it shows an image to compare branches. That link is always 404, since it will be of the form
try.gitea.io/<user>/<repo>/compare/<branch1>...<user>:<branch2>
It should be:
try.gitea.io/<user>/<repo>/compare/<branch1>...<branch2>
If I change the address in the bar and remove the second user reference, the site loads fine.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @evilstiefel on GitHub (Feb 14, 2017). - Gitea version (or commit ref): 1.0.0+272-gcf47532e - Git version: 2.8.3 - Operating system: Linux ad0c0ea10d83 4.4.0-62-generic #83-Ubuntu - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/gitea/gitea/compare/master...gitea:master - [ ] No - [ ] Not relevant - Log gist: ## Description When creating a repository, next to the branch-dropdown, it shows an image to compare branches. That link is always 404, since it will be of the form `try.gitea.io/<user>/<repo>/compare/<branch1>...<user>:<branch2>` It should be: `try.gitea.io/<user>/<repo>/compare/<branch1>...<branch2>` If I change the address in the bar and remove the second user reference, the site loads fine. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42030136-compare-button-leads-to-404?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the type/bug label 2025-11-02 03:19:53 -06:00
Author
Owner

@tboerger commented on GitHub (Feb 14, 2017):

OK, i can confirm it on try.gitea.io, example: Go to the gitea/gitea repo and click the pull request button leads to 404. If you try to do the same from a fork it works totally fine.

@tboerger commented on GitHub (Feb 14, 2017): OK, i can confirm it on try.gitea.io, example: Go to the gitea/gitea repo and click the pull request button leads to 404. If you try to do the same from a fork it works totally fine.
Author
Owner

@lunny commented on GitHub (Feb 15, 2017):

@evilstiefel please confirm #948 fix this.

@lunny commented on GitHub (Feb 15, 2017): @evilstiefel please confirm #948 fix this.
Author
Owner

@evilstiefel commented on GitHub (Feb 15, 2017):

@lunny I can confirm your change fixes this issue

@evilstiefel commented on GitHub (Feb 15, 2017): @lunny I can confirm your change fixes this issue
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#353