Public Repo, Private Code #9951

@techknowlogick commented on GitHub (Dec 9, 2022):

~~Closing as dupe of https://github.com/go-gitea/gitea/issues/3217~~

Edit: Wrong issue, one moment while I find the correct issue.

@techknowlogick commented on GitHub (Dec 9, 2022): ~Closing as dupe of https://github.com/go-gitea/gitea/issues/3217~ Edit: Wrong issue, one moment while I find the correct issue.

GiteaMirror commented

@FrostKiwi commented on GitHub (Dec 9, 2022):

~~Closing as dupe of #3217~~

Edit: Wrong issue, one moment while I find the correct issue.

Ohh, sry if dupe. Looked through the issues and found things about different setups with privacy and visibilty, just not one with public issues, public wiki, but private code.

@FrostKiwi commented on GitHub (Dec 9, 2022): > ~Closing as dupe of #3217~ > > Edit: Wrong issue, one moment while I find the correct issue. Ohh, sry if dupe. Looked through the issues and found things about different setups with privacy and visibilty, just not one with public issues, public wiki, but private code.

GiteaMirror commented

@techknowlogick commented on GitHub (Dec 9, 2022):

@FrostKiwi i may have been thinking of those other tickets. Sorry for prematurely closing this ticket, I've reopened it.

@techknowlogick commented on GitHub (Dec 9, 2022): @FrostKiwi i may have been thinking of those other tickets. Sorry for prematurely closing this ticket, I've reopened it.

GiteaMirror commented

@lafriks commented on GitHub (Dec 9, 2022):

Would be nice to have ability to be set parts of repo public (also packages for example)

@lafriks commented on GitHub (Dec 9, 2022): Would be nice to have ability to be set parts of repo public (also packages for example)

GiteaMirror commented

@lightr4in commented on GitHub (Dec 14, 2022):

For instance, Gitlab offers an options section to set the permissions for each unit separately:

But this might be something for an extra issue.

@lightr4in commented on GitHub (Dec 14, 2022): For instance, Gitlab offers an options section to set the permissions for each unit separately: ![part of Gitlab's permissionspage](https://user-images.githubusercontent.com/120530289/207471740-e78c932f-6b95-40f1-9b3c-914b5724eb4e.png) But this might be something for an extra issue.

GiteaMirror commented

@lunny commented on GitHub (Dec 14, 2022):

Should the title be changed as private repo, public code? What's the different between them?

@lunny commented on GitHub (Dec 14, 2022): Should the title be changed as private repo, public code? What's the different between them?

GiteaMirror commented

@FrostKiwi commented on GitHub (Dec 14, 2022):

Should the title be changed as private repo, public code? What's the different between them?

My use case within an international company setting is the exact opposite. I want everything public for easiest collaboration, except code due to cross-border export regulations.

Of course if a name change is desired, then I guess we could go along the lines of @lightr4in reference to GitLab https://github.com/go-gitea/gitea/issues/22074#issuecomment-1350145371 and rename the issue to a variant of "More in-depth privacy controls" or something along those lines...

@FrostKiwi commented on GitHub (Dec 14, 2022): > Should the title be changed as private repo, public code? What's the different between them? My use case within an international company setting is the exact opposite. I want everything public for easiest collaboration, except code due to cross-border export regulations. Of course if a name change is desired, then I guess we could go along the lines of @lightr4in reference to GitLab https://github.com/go-gitea/gitea/issues/22074#issuecomment-1350145371 and rename the issue to a variant of "More in-depth privacy controls" or something along those lines...

GiteaMirror commented

@bendem commented on GitHub (Feb 8, 2023):

Gitea already has everything for this, it would "just" work (tm) if public access was evaluated as another "team".

@bendem commented on GitHub (Feb 8, 2023): Gitea already has everything for this, it would "just" work (tm) if public access was evaluated as another "team". ![image](https://user-images.githubusercontent.com/2681677/217470179-f68e19a8-c016-4304-ae38-2db2a0e34370.png)

GiteaMirror commented

@FrostKiwi commented on GitHub (May 12, 2023):

@delvh Is it within the realm of possibility, that this gets into v1.20?

@FrostKiwi commented on GitHub (May 12, 2023): @delvh Is it within the realm of possibility, that this gets into [v1.20](https://github.com/go-gitea/gitea/issues/23072)?

GiteaMirror commented

@delvh commented on GitHub (May 12, 2023):

If I'm not mistaken, the corresponding PR by @lunny has already been merged to disable the code tab while enabling the issue tracker.
It doesn't mean that you can make only parts of a repo public, but you can have a repo where users cannot see the code at all.
At least for the short and medium term, this seems like the best and easiest solution to me.

@delvh commented on GitHub (May 12, 2023): If I'm not mistaken, the corresponding PR by @lunny has already been merged to disable the code tab while enabling the issue tracker. It doesn't mean that you can make only parts of a repo public, but you can have a repo where users cannot see the code at all. At least for the short and medium term, this seems like the best and easiest solution to me.

GiteaMirror commented

@lunny commented on GitHub (May 12, 2023):

What's Public and Private? I think both concepts are for the anonymous users in a login-free Gitea instance or non-owners/non-members/non-collaborators of the repository in a login-required Gitea instance. So maybe we need one or two default roles for them.

@lunny commented on GitHub (May 12, 2023): What's `Public` and `Private`? I think both concepts are for the anonymous users in a login-free Gitea instance or non-owners/non-members/non-collaborators of the repository in a login-required Gitea instance. So maybe we need one or two default roles for them.

GiteaMirror commented

@FrostKiwi commented on GitHub (May 12, 2023):

If I'm not mistaken, the corresponding PR by @lunny has already been merged to disable the code tab while enabling the issue tracker. It doesn't mean that you can make only parts of a repo public, but you can have a repo where users cannot see the code at all. At least for the short and medium term, this seems like the best and easiest solution to me.

Are you referring to this checkbox?

Does this mean I can finally set the code to be invisible to all, except those chosen as Collaborators?

@FrostKiwi commented on GitHub (May 12, 2023): > If I'm not mistaken, the corresponding PR by @lunny has already been merged to disable the code tab while enabling the issue tracker. It doesn't mean that you can make only parts of a repo public, but you can have a repo where users cannot see the code at all. At least for the short and medium term, this seems like the best and easiest solution to me. Are you referring to this checkbox? ![image](https://github.com/go-gitea/gitea/assets/60887273/b5f1104e-88fa-44e1-904a-370d385bfc86) Does this mean I can finally set the code to be invisible to all, except those chosen as Collaborators?

GiteaMirror commented

@a1012112796 commented on GitHub (May 12, 2023):

I think we can define a special user named as @anyone (or other name), all users and unlogin users will have all permssions that you permit @anyone.

@a1012112796 commented on GitHub (May 12, 2023): I think we can define a special user named as `@anyone` (or other name), all users and unlogin users will have all permssions that you permit `@anyone`.

GiteaMirror commented