Public repo is not public

Site Feedback
1

Hi,

I have created a public repo at https://gitea.com/fairking/gresmcp

If you actually open the url in private browser tab, any navigation redirects to SignIn page.

Why the access to the source code or to the issues/prs pages are not available by unauthenticated users? When I click a file or issues page, it redirects to SignIn. Why the public repo is not public? I don’t understand.

2

on gitea.com that pattern usually means the org/user visibility or the instance force-signin is overriding the repo visibility flag.

quick checks:

  • repo settings still say Public (not Internal)
    • org settings arent forcing private / members-only
      • try the raw file url and https://gitea.com/api/v1/repos/fairking/gresmcp in a private window. if the api returns 401/404 while the repo page redirects to SignIn, its an instance-side gate not your click path
    • if both api and html want auth on a public repo, thats a gitea.com staff / site config thing more than a local setting. paste whether the api call 401s.
3

the api url serves some json with 200 status. I think you could check it by yourself.

means the org/user visibility or the instance force-signin is overriding the repo visibility flag

I don’t understand what you mean by that. Can you simply explain how to disable that? I mean how to make my project publicly available? Which setting and where I should change. Or it is a gitea bug?