Toggle or restrict features (including repository) for internal and public projects
Description including problem, use cases, benefits, and/or goals
More and more requests come in for the ability to restrict repository access to project members or disable it altogether.
If we'd add or change that ability, it makes sense to carry this through to the other features as well.
Proposal
We add the ability to toggle any feature (already present for all features, but repository) and the ability to restrict its access to only the members of the group / project.
-
enable/disable repository per project -
restrict access to members
Mockups for enabling/disabling repository
Project page without wiki homepage
Public view of project page without wiki homepage
Project page with wiki homepage
The activity tab only has comments and team. Push events and merge events are no longer relevant.
If the repository is disabled, other features related to the repository are also disabled. The dropdown itself is disabled, as well.
Links / references
- request for restriction https://gitlab.com/gitlab-org/gitlab-ce/issues/18721
@markpundsack would this cause any problems with CI?
cc @dzaporozhets @stanhu for opinions.