Skip to content
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

"followers" & "following" is a valid repository name #10195

Closed
3 tasks
ghost opened this issue Feb 8, 2020 · 0 comments · Fixed by #10202
Closed
3 tasks

"followers" & "following" is a valid repository name #10195

ghost opened this issue Feb 8, 2020 · 0 comments · Fixed by #10202
Assignees
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Feb 8, 2020

  • Gitea version (or commit ref): 1.11.0+dev-534-ga864d61ee
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

Gitea uses the URL https://try.gitea.io/imtestingthis/followers to display my followers, and https://try.gitea.io/imtestingthis/following to display who I follow.

It is possible to create a repository called followers or following. In this case you cannot view the repository's content as the user's followers/following list appears instead. It is still possible to go to a repository's subpages such as issues, wiki, etc.

Solutions

  1. Disallow the creation of repositories called followers and following.
  2. Use https://try.gitea.io/imtestingthis?followers and https://try.gitea.io/imtestingthis?following as a URL for those pages. This would be consistent with other profile actions such as https://try.gitea.io/imtestingthis?tab=activity .
@lafriks lafriks self-assigned this Feb 9, 2020
@lafriks lafriks added this to the 1.12.0 milestone Feb 9, 2020
@lafriks lafriks modified the milestones: 1.12.0, 1.11.0 Feb 9, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant