# gitplace for t/suki?

**URL:** <https://forum.tsuki.games/t/gitplace-for-t-suki/239>\
**Category:** Meta\
**Tags:** git\
**Created:** [February 26, 2025, 7:32pm UTC](https://forum.tsuki.games/t/gitplace-for-t-suki/239 "2025-02-26T19:32:42Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![exodrifter](https://tsuki.b-cdn.net/user_avatar/forum.tsuki.games/exodrifter/32/3_2.png) [@exodrifter](https://forum.tsuki.games/u/exodrifter)\
**Post date:** [April 9, 2025, 10:30pm UTC](https://forum.tsuki.games/t/gitplace-for-t-suki/239/13 "2025-04-09T22:30:30Z")

</div>

I was reading the documentation for repository visibility in Forgejo and found out that there’s actually three different ways repositories can be visible:

> - If your profile’s visibility is set to “Limited”, all of your non-private repositories will only be visible to logged in users.
> - If your profile’s visibility is set to “Public”, all of your non-private repositories will be shown to everyone.
> - If you do not want anyone (apart from your fellow collaborators) to see your repositories, mark your repository as “Private”.

See: [docs/docs/user/repo-permissions.md at v1.21 - forgejo/docs - Codeberg.org](https://codeberg.org/forgejo/docs/src/branch/v1.21/docs/user/repo-permissions.md)

Right now the instance is private as a way to deal with AI scrapers, but I was hoping that I we could decide later about making the git instance visible to the public and change all public repositories at that time to limited. But, you can’t actually do that on a per-repository basis. So, I think it would be better if everyone treated the git hosting as if it were visible to the public. I’ve updated the [official t/suki gitplace](https://forum.tsuki.games/t/official-t-suki-gitplace/257) docs to reflect that.

---

_[View the full topic](https://forum.tsuki.games/t/gitplace-for-t-suki/239)._