Gitness - Unauthenticated Git Pulls

[golyalpha]

When setting a repository to Public under Gitness (which is described as "Anyone with access to the Gitness environment can clone this repo"), browsing the repository via the Web UI is not possible, however, unauthenticated git pulls are.

Personally, I'd be fine if Public on Gitness meant what Protected/Internal means everywhere else (if you can log in to Gitness, you can see and work with the repo), but this is a weird combination of both Public as in "everyone in the world" (can git pull), and Public as in "everyone with an account" (can see the repo in their browser)...

Is this a bug, or is this intended behaviour? It might be worthwhile to clarify the note on the visibility level if this is intended - point out that you don't need an account to do a pull.

[bradrydzewski]

This is due to incremental development / shipping subsets of features as soon as they are ready. The backend team added support for public clone because it was relatively simple. However, the effort to update the frontend to support unauthenticated / guest browsing of public repositories is a much larger effort. These frontend changes are a separate workstream and have not been pushed yet.

Merging with #3521