Follow-up from "Refactor reduce repo size content"
The following discussions from !33924 (merged) should be addressed:
Rewriting repository history is a destructive operation. Make sure to back up your repository before
repository history, and is recommended over both [`git filter-branch`](https://git-scm.com/docs/git-filter-branch) and [BFG](https://rtyley.github.io/bfg-repo-cleaner/).
Avoiding 'both' in case more options are added in the future. Also, since these are not-recommended-options, I don't think we need to call them out in an unordered list like this. Let's keep the visual focus on the recommended approach
In addition to the better-known [branches](branches/index.md) and tags, GitLab also creates refs that prevent dead links to commits, and missing diffs when viewing merge requests. You can use [repository cleanup](#repository-cleanup) to remove these refs from GitLab.
I think this is a cleaner way of phrasing it.
- `refs/environments/*` for environments. - `refs/keep-around/*` for preventing commits with discussion from being deleted. These refs are hidden. To speed fetching, these refs are not usually included; `refs/keep-around/*` are never fetched. However, these refs can be accessed from the Git bundle inside a project export:
I disagreed with the approach here; we presented a list of references, and then discussed a new one in the following paragraph. I moved
refs/keep-around/*into the list, and rephrased the paragraph afterward.
The final sentence is an introduction to a procedure, and should end with a colon instead of a period.
Missing space is preventing this note box from rendering properly
If you exceed the repository size limit, you can:
If these actions are insufficient, you can also:
Unfortunately, this workflow won't work. Deleting files in a commit doesn't actually reduce the size of the repository, because the earlier commits and blobs still exist. Instead, you must rewrite history. We recommend the open-source community-maintained tool