Public Repo, Private Code

[FrostKiwi]

Feature Description

I would like to set every aspect of a Repo Public, except the code and the ability to git clone it.
Use-case:
Being at an international company, code is under export restriction and cannot be published without prior green lighting. So it must remain private. But I still want international colleagues to be able to send in issues, collab on their resolution and have the Wiki public to any guest.
I can of course create two separate repos, once for private code and one for public issues and the Wiki. But I am not aware of Gitea being able to set this up in a single Repo.

Thus this is my feature request:
One Repo, Private Code Tab, Public Issue tracker + Wiki.

Screenshots

No response

[techknowlogick]

Closing as dupe of #3217

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

[FrostKiwi]

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.

[techknowlogick]

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

[lafriks]

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

[lightr4in]

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

But this might be something for an extra issue.

[lunny]

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

[FrostKiwi]

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 #22074 (comment) and rename the issue to a variant of "More in-depth privacy controls" or something along those lines...

[bendem]

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

[FrostKiwi]

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

[delvh]

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.

[lunny]

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.

[FrostKiwi]

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?

[a1012112796]

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.

[lunny]

No, it means nobody could visit code

[FrostKiwi]

No, it means nobody could visit code

Ohh, that's not what I need for my use-case of allowing colleagues to comment on issues and allow them them to read the wiki, without violating export restrictions. I still need a separate "Repo for Collaboration", where I copy paste everything to and from.

Maybe a bit of a pipe dream to expect Gitea to handle it all, Gitea has already the ability to use external issue trackers and wiki, so maybe it's high time I stop depending on Gitea and use third party packages for those...

edit: I think I found a way to summarize a way to express what I want in simple terms: Collaborator only code access.

[moritz-h]

Closing as dupe of #3217

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

Duplicate of #639?

[FrostKiwi]

Closing as dupe of #3217
Edit: Wrong issue, one moment while I find the correct issue.

Duplicate of #639?

Indeed, that is the same issue. Failed to find it when opening up this one...

[FrostKiwi]

Closed in favor of #639 , since that discussion predates this one. So further discussion here: #639 (comment)