diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-18 13:50:51 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-18 13:50:51 +0300 |
| commit | db384e6b19af03b4c3c82a5760d83a3fd79f7982 (patch) | |
| tree | 34beaef37df5f47ccbcf5729d7583aae093cffa0 /doc/administration/repository_checks.md | |
| parent | 54fd7b1bad233e3944434da91d257fa7f63c3996 (diff) | |
Add latest changes from gitlab-org/gitlab@16-3-stable-eev16.3.0-rc42
Diffstat (limited to 'doc/administration/repository_checks.md')
| -rw-r--r-- | doc/administration/repository_checks.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md index 8cc635b50fc..1a33b6b5746 100644 --- a/doc/administration/repository_checks.md +++ b/doc/administration/repository_checks.md @@ -93,6 +93,10 @@ If periodic repository checks cause false alarms, you can clear all repository c 1. Expand the **Repository maintenance** section. 1. Select **Clear all repository checks**. +## Troubleshooting + +When working with repository checks, you might encounter the following issues. + ### Error: `failed to parse commit <commit SHA> from object database for commit-graph` You can see a `failed to parse commit <commit SHA> from object database for commit-graph` error in repository check logs. This error occurs if your `commit-graph` cache is out |