Clarify repository cleanup process
What does this MR do?
In !52734 (merged), I changed the heading in Reduce Repo Size docs from "Purge files from repository history" to "Purge files from repo history and storage". This can be misleading as the process under this heading does not reduce repository storage consumption - Repository cleanup is required to reduce the storage size.
This MR removes the words "and storage" from the heading to emphasize that Repository cleanup is a required (not optional) step to reduce storage.
Screenshots (strongly suggested)
Before
After
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team