<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve Follow-up from the discussion in https://gitlab.com/gitlab-org/gitlab/-/issues/357680#note_956842783. Today the actions/settings to maintain and cleanup the repository are scattered, which can lead to user confusion and lack of discoverability. An example of this is https://gitlab.com/gitlab-org/gitlab/-/issues/217453+, where a user wasn't aware that the **Housekeeping** action in **Settings > General** would reduce the repository size, even when looking at the docs. There's an opportunity to consolidate these settings. The current state: 1. The [housekeeping docs](https://docs.gitlab.com/ee/administration/housekeeping.html) say that it only performs housekeeping tasks on the Git repository, nothing else. Therefore, it's odd that housekeeping is located in the **General** project settings. 1. On that page, it also says that _instance-level_ settings for repository housekeeping are located in **Admin > Settings > Repository > Repository maintenance**. This is different from the _project-level_ settings. 1. Finally, there's the **Repository > Repository cleanup** section in the project settings to run `git filter-repo`. 1. We [recently added](https://gitlab.com/gitlab-org/gitlab/-/issues/357680) a new “Recalculate repository size” in **Settings > Usage Quotas**, which doesn't help reduce the repository size but simply updates the calculated size. Still, this action is tightly related to maintaining/cleaning up the repository. ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> * Rename "Settings > Repository > Repository cleanup" to `Settings > Repository > Repository maintenance` - This aligns the location to be similar to the Admin area. - Decision informed by design decisions made in https://gitlab.com/gitlab-org/gitlab/-/issues/450701+ - Move "Housekeeping" and "Pruning unreachable objects" to "Repository maintenance" - Add information in "Settings > General" to say those settings have moved - Update documentation to reflect the consolidation of the settings -https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_using_git.html - Manual trigger section inhttps://docs.gitlab.com/ee/administration/housekeeping.html  To address navigating to this area from other areas like "Usage quotas", it could be linked with a button saying something like "Manage repository storage" or "Maintain repository storage" (UI text to be determined). Examples of how this could look in alerts could be: | Project overview | Usage quota | | ------ | ------ | |  |  | ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Feature Usage Metrics <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->