Code browser: HTTP code 404 when I click on a submodule directory which is the wiki repository of the project #217
Labels
No labels
accessibility
bug
bug
infrastructure
Codeberg
contributions welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
please chill
we are volunteers
public relations
question
question
user support
s/Forgejo
s/Forgejo/migration
s/Pages
s/Weblate
s/Woodpecker
security
service
upstream
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Depends on
#579 Gitea v1.17
Codeberg/Community
Reference
Codeberg/Community#217
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In one project, I added the wiki repository as submodule in the main repository to have a convenient way of updating the documentation. When I browse the code in the code view and click on the directory that has the wiki repository as submodule, I get an 404 error. This is because the wiki repository is not a "real" project of its own.
This is the project: https://codeberg.org/moenavigator/moenavigatorengine
The "doc" folder is the wiki repository as submodule.
A solution to prevent such 404 errors could be to check if the submodule URL is basically the URL of the project repository with ".wiki" added to it. In that case, the code browser could redirect to the project wiki. In the case that a project added the URL of another project on the same domain the code browser could redirect to the other project's wiki.
I tried to reproduce on https://try.gitea.io/fnetx/gitea-submodule-thing/wiki to report upstream, but I cannot even clone the wiki. Look at the provided link it isn't even displaying the wiki git url.
cc @6543 is there a change coming or is it a bug at try.gitea.io?
still on my backlock ...
I tested it out again and since the problem still occurs, I decided to forward this issue to upstream: https://github.com/go-gitea/gitea/issues/18590
To test it out use either of the following links:
The issue should have been fixed by upstream in this PR: https://github.com/go-gitea/gitea/pull/18831. The functionality will be implemented with the next release