Skip to content

Make private repositories listable #23117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
KroMignon opened this issue Feb 24, 2023 · 6 comments
Open

Make private repositories listable #23117

KroMignon opened this issue Feb 24, 2023 · 6 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@KroMignon
Copy link

KroMignon commented Feb 24, 2023

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

@KroMignon KroMignon added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Feb 24, 2023
@stuzer05
Copy link
Contributor

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?

@wolfogre
Copy link
Member

TBH, Gitea doesn't have the feature exactly you want, but maybe this could help:

Create a team like this:

image

And the members who joined this team can see the repo list:

image

But they can't open the repo:

image

If you think it can't help you, please feel free to reopen this issue.

@KroMignon
Copy link
Author

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?

@wolfogre

This comment was marked as off-topic.

@KroMignon

This comment was marked as off-topic.

@wolfogre

This comment was marked as off-topic.

@wolfogre wolfogre reopened this Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants