Documentation review for "Remove cleaned up OIDs from database and cache"
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=28543) </details> <!--IssueSummary end--> ## References Merged MR that introduced documentation requiring review: gitlab-ce!26555 Related issue(s): https://gitlab.com/gitlab-org/gitlab-ce/issues/30093 ## Further Details The following discussion from gitlab-ce!26555 should be addressed: - [ ] @nick.thomas started a [discussion](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26555#note_165205264): > @marcia we could do with a documentation review here, I think. > > This feature started as repository **size reduction**, but with these changes we're starting to inch it towards **removing sensitive content from history**. > > It's still not complete, and there are lots of places where we need to address copies of the rewritten data before it will be, but it feels like the docs are starting to creak! > > I did find https://docs.gitlab.com/ee/topics/git/numerous_undo_possibilities_in_git/ which mentions BFG and `git filter-branch`, but I'm concerned that this doesn't seem GitLab-specific at present. > > WDYT? Can we merge as-is and look at a follow-up issue to split the topics, or should we address this upfront?
issue