Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
parent
2da25d0133
commit
4683f63dae
|
|
@ -134,14 +134,18 @@ from your project every `200` push, freeing up storage space for your project.
|
|||
|
||||
### Prune unreachable objects
|
||||
|
||||
Unreachable objects are pruned as part of scheduled housekeeping. However,
|
||||
you can trigger manual pruning as well. An example: removing commits that contain sensitive
|
||||
information. Triggering housekeeping prunes unreachable objects with a grace period of
|
||||
two weeks. When you manually trigger the pruning of unreachable objects, the grace period
|
||||
is reduced to 30 minutes.
|
||||
Unreachable objects are pruned as part of scheduled housekeeping. However, you can trigger
|
||||
manual pruning as well. Triggering housekeeping prunes unreachable objects with a grace
|
||||
period of two weeks. When you manually trigger the pruning of unreachable objects, the
|
||||
grace period is reduced to 30 minutes.
|
||||
|
||||
{{< alert type="warning" >}}
|
||||
|
||||
Pruning unreachable objects does not guarantee the removal of leaked secrets and other sensitive information. For information on how to remove secrets that
|
||||
were committed but not pushed, see the [remove a secret from your commits tutorial](../user/application_security/secret_detection/remove_secrets_tutorial.md).
|
||||
Additionally, you can [remove blobs individually](../user/project/repository/repository_size.md#remove-blobs). Refer to that documentation for possible
|
||||
consequences of performing that operation.
|
||||
|
||||
If a concurrent process (like `git push`) has created an object but hasn't created
|
||||
a reference to the object yet, your repository can become corrupted if a reference
|
||||
to the object is added after the object is deleted. The grace period exists to
|
||||
|
|
|
|||
Loading…
Reference in New Issue