Add support for ci_default_git_depth #799
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svanharmelen
approved these changes
Mar 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitLab started exposing a
ci_default_git_depthattribute for projects via their API a few months back (this MR), which maps to the "Git shallow clone"-settings under the CI/CD configuration for the project.This PR adds support for that field when retrieving projects and when updating projects - I've tested that this works as expected on a local project here. I haven't added support for this to project creation as I'm not sure it even is exposed via the API and it wasn't part of the functionality I needed for my project here. If you'd like to add this as well, let me know and I can do a quick test of it before this gets merged.
Thanks!