Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
49558c1e
Commit
49558c1e
authored
Jun 18, 2019
by
Marcia Ramos
Committed by
Nick Thomas
Jun 18, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Fixes all the alert boxes in "reduce repo size"
parent
e2d217f6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
11 deletions
+12
-11
doc/user/project/repository/reducing_the_repo_size_using_git.md
...er/project/repository/reducing_the_repo_size_using_git.md
+12
-11
No files found.
doc/user/project/repository/reducing_the_repo_size_using_git.md
View file @
49558c1e
...
...
@@ -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
up its own internal state, maximizing the space saved.
> **Warning
:**
>
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
>
inform any collaborators to not use `pull` after your changes, but use `rebase`.
CAUTION:
**Caution
:**
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
inform any collaborators to not use
`pull`
after your changes, but use
`rebase`
.
> **Warning
:**
>
This process is not suitable for removing sensitive data like password or keys
>
from your repository. Information about commits, including file content, is
>
cached in the database, and will remain visible even after they have been
>
removed from the repository.
CAUTION:
**Caution
:**
This process is not suitable for removing sensitive data like password or keys
from your repository. Information about commits, including file content, is
cached in the database, and will remain visible even after they have been
removed from the repository.
## Using the BFG Repo-Cleaner
...
...
@@ -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
completed.
NOTE:
**Note:**
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,
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
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
purposes!
## Using `git filter-branch`
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment