Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appveyor: Clone depth number is too small #427

Merged
merged 1 commit into from Apr 30, 2016
Merged

Appveyor: Clone depth number is too small #427

merged 1 commit into from Apr 30, 2016

Conversation

crazymaster
Copy link
Member

If you do a lot of commits producing queued builds, git checkout operation following git clone can fail because requested commit is not present in a cloned repository.

ref: https://www.appveyor.com/docs/how-to/repository-shallow-clone#setting-depth-of-git-clone-command

If you do a lot of commits producing queued builds, git checkout operation following git clone can fail because requested commit is not present in a cloned repository.

ref: https://www.appveyor.com/docs/how-to/repository-shallow-clone#setting-depth-of-git-clone-command
@haya14busa
Copy link
Member

+1

It's not directly related with this PR, but should we add an corresponding option in travis ci?
https://docs.travis-ci.com/user/customizing-the-build/#Git-Clone-Depth

git:
  depth: 10

@haya14busa haya14busa merged commit 4bf6dea into master Apr 30, 2016
@haya14busa haya14busa deleted the clone_depth branch April 30, 2016 00:19
haya14busa added a commit to haya14busa/vital.vim that referenced this pull request Apr 30, 2016
thinca added a commit that referenced this pull request Apr 30, 2016
.travis.yml: set clone-depth option which correspond to #427
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants