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
47fedfea
Commit
47fedfea
authored
Sep 07, 2020
by
Jonston Chan
Committed by
Marcel Amirault
Sep 07, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: update outdated shallow cloning information
parent
d991c4b1
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
doc/ci/large_repositories/index.md
doc/ci/large_repositories/index.md
+2
-3
No files found.
doc/ci/large_repositories/index.md
View file @
47fedfea
...
...
@@ -28,9 +28,8 @@ Each guideline is described in more detail in the sections below:
> Introduced in GitLab Runner 8.9.
GitLab and GitLab Runner always perform a full clone by default.
While it means that all changes from GitLab are received,
it often results in receiving extra commit logs.
GitLab and GitLab Runner perform a
[
shallow clone
](
../pipelines/settings.md#git-shallow-clone
)
by default.
Ideally, you should always use
`GIT_DEPTH`
with a small number
like 10. This will instruct GitLab Runner to perform shallow clones.
...
...
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