Open KroMignon opened 1 year ago
What's the idea of private org repos then? It's useful if you have multiple different clients assigned to their respective teams in organizations. And each client can see only necessary repositories.
Wouldn't your idea break it?
TBH, Gitea doesn't have the feature exactly you want, but maybe this could help:
Create a team like this:
And the members who joined this team can see the repo list:
But they can't open the repo:
If you think it can't help you, please feel free to reopen this issue.
Thank you @wolfogre for your suggestion, it could be a way to solve my issue. But it is not very "comfortable" to use.
It is possible to create a kind of "default teams", which could be used by each organization?
For example, a Gitea admin user creates some kind of default teams with default allowed accesses. Then for each organization, those "global teams" are visible a could be used as they are or with"adjusted" allowed accesses.
Is this feasible or will it break Gitea usage?
Hi @KroMignon, I noticed that you said you cannot reopen this issue, it shouldn't happen. Could you please show me whether there's a button like this in your view? It will help me to adjust my work, thanks.
Here is what I have on GitHub, there is no such button
Here is what I have on GitHub, there is no such button
Thank you so much, I'll figure it out. Before that, let me help you to reopen this PR first.
Feature Description
Hello,
I would like to be able to make private repositories visible for everyone who are in the organization. The user should only be able to see repository name and the owner(s), and then he could ask a owner to get access. The idea is to avoid multiple creation of same repository in a organization.
Ideally, I would like to have a setting parameter for each organization to enable "show private repositories" (default: false).
Best regards
Screenshots
No response