pagure

#5182 RFE : allow private project to be created in specific namespace
Opened by arrfab. Modified

Open
Close Issue

Actually, when someone decides to create (through web UI or API) a project that should be private, there is no way to make it available under a specific namespace as it defaults to creating it.
There are some reason why a team (like like an "Org") would like to see some private projects available under "org" namespace and not an individual.
Would it be possible to allow a private repo to be created under a specific namespace ? (not preventing it)

This should already work? As long as the user has privileges to that namespace, it should be able to do it (provided that the instance allows private projects).

I should have all rights as both listed under PAGURE_ADMIN_USERS and member of a group also listed in ADMIN_GROUP
I don't see in doc how to enable/disable some features in NAMESPACE though : is that possible to restrict/enable/disable feature per namespace ? (like creating private projects) : couldn't find anything in doc about this

It is not per-namespace, it's per-instance. Now technically, as an admin, you can go into the database and mark the project as private even if the UI doesn't expose it (that is, Pagure's configuration has private projects disabled). That works (and I've done that for projects being staged to move to code.opensuse.org).
Edited by ngompa
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.