Skip to content

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.

feature_toggle

  • enable/disable repository per project
  • restrict access to members

Mockups for enabling/disabling repository

Project page without wiki homepage Screen_Shot_2016-09-14_at_9.37.14_AM

Public view of project page without wiki homepage Screen_Shot_2016-09-14_at_9.38.36_AM

Project page with wiki homepage Screen_Shot_2016-09-14_at_9.39.37_AM

The activity tab only has comments and team. Push events and merge events are no longer relevant. Screen_Shot_2016-09-14_at_9.40.39_AM

If the repository is disabled, other features related to the repository are also disabled. The dropdown itself is disabled, as well. Screen_Shot_2016-09-14_at_11.41.49_AM

Links / references

@markpundsack would this cause any problems with CI?

cc @dzaporozhets @stanhu for opinions.