Commit e5ca7b8b authored by Nick Thomas's avatar Nick Thomas

Merge branch 'docs-review-reduce-repo-size' into 'master'

Docs: Fixes all the alert boxes in "reduce repo size"

Closes #61472

See merge request gitlab-org/gitlab-ce!29680
parents e2d217f6 49558c1e
...@@ -35,16 +35,16 @@ BFG Repo-Cleaner](#using-the-bfg-repo-cleaner). It's faster and simpler than ...@@ -35,16 +35,16 @@ BFG Repo-Cleaner](#using-the-bfg-repo-cleaner). It's faster and simpler than
`git filter-branch`, and GitLab can use its account of what has changed to clean `git filter-branch`, and GitLab can use its account of what has changed to clean
up its own internal state, maximizing the space saved. up its own internal state, maximizing the space saved.
> **Warning:** CAUTION: **Caution:**
> Make sure to first make a copy of your repository since rewriting history will Make sure to first make a copy of your repository since rewriting history will
> purge the files and information you are about to delete. Also make sure to purge the files and information you are about to delete. Also make sure to
> inform any collaborators to not use `pull` after your changes, but use `rebase`. inform any collaborators to not use `pull` after your changes, but use `rebase`.
> **Warning:** CAUTION: **Caution:**
> This process is not suitable for removing sensitive data like password or keys This process is not suitable for removing sensitive data like password or keys
> from your repository. Information about commits, including file content, is from your repository. Information about commits, including file content, is
> cached in the database, and will remain visible even after they have been cached in the database, and will remain visible even after they have been
> removed from the repository. removed from the repository.
## Using the BFG Repo-Cleaner ## Using the BFG Repo-Cleaner
...@@ -99,10 +99,11 @@ up its own internal state, maximizing the space saved. ...@@ -99,10 +99,11 @@ up its own internal state, maximizing the space saved.
`git gc` against the repository. You will receive an email once it has `git gc` against the repository. You will receive an email once it has
completed. completed.
NOTE: **Note:**
This process will remove some copies of the rewritten commits from GitLab's This process will remove some copies of the rewritten commits from GitLab's
cache and database, but there are still numerous gaps in coverage - at present, cache and database, but there are still numerous gaps in coverage - at present,
some of the copies may persist indefinitely. [Clearing the instance cache](../../../administration/raketasks/maintenance.md#clear-redis-cache) some of the copies may persist indefinitely. [Clearing the instance cache](../../../administration/raketasks/maintenance.md#clear-redis-cache)
may help to remove some of them, but it should not be depended on for security may help to remove some of them, but it should not be depended on for security
purposes! purposes!
## Using `git filter-branch` ## Using `git filter-branch`
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment