-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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.
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
Links in Markdown files are not evaluated relative to the (relevant / main) branch #28904
Comments
It seems plausible that this bug was introduced in #26745. |
Hello I confirm this regression, we have same trouble. Thanks |
I have deployed a custom build based on v1.21.4 with #28909 cherry-picked and this fixes the issue for us. It would be really great if the backport of the fix can make it into v1.21.5. |
Fix #28904 Co-authored-by: Giteabot <[email protected]>
Fix go-gitea#28904 Co-authored-by: Giteabot <[email protected]>
Fix will be in 1.24.5 (#28922) |
Backport #28909 by @KN4CK3R Fix #28904 Co-authored-by: KN4CK3R <[email protected]>
I wrote v1.24.5 - but it should be v1.21.5 😆 |
I'm sure the statement is still valid... 😏 |
Fix go-gitea#28904 Co-authored-by: Giteabot <[email protected]>
Fix go-gitea#28904 Co-authored-by: Giteabot <[email protected]>
Automatically locked because of our CONTRIBUTING guidelines |
Description
If, for example in your README, you have a link on some other files in the repository, they are not relative to the current branch. I.e.
doc/test.md
and/doc/test.md
do not link to https://try.gitea.io/MGChecker/READMEsrc/branch/main/doc/test.md , but to https://try.gitea.io/MGChecker/README/doc/test.md . This is a regression, this worked a few months ago.See https://try.gitea.io/MGChecker/README/src/branch/main
Gitea Version
1.21.4
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?
From your downloads, but not relevant
Database
None
The text was updated successfully, but these errors were encountered: