Repository navigation
Clone 1000 commits on Travis CI - #2124
Merged
Travis Plunk (TravisEz13) merged 1 commit intoAug 30, 2016
Merged
Conversation
The previous failure we saw was because the most recent annotated tag did not exist in the previous 50 commits. In my experience we've gone about ~300 commits between tags, so I believe 1000 to be safe, but know 100 will not be.
|
Hi Andy Jordan (@andschwa), I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
TTYL, MSBOT; |
This was referenced May 17, 2017
Thatgfsj (Thatgfsj)
pushed a commit
to Thatgfsj-contribs/PowerShell
that referenced
this pull request
Aug 6, 2026
The previous failure we saw was because the most recent annotated tag did not exist in the previous 50 commits. In my experience we've gone about ~300 commits between tags, so I believe 1000 to be safe, but know 100 will not be.
This file contains hidden or 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
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.
The previous failure we saw was because the most recent annotated tag did not exist in the previous 50 commits. In my experience we've gone about ~300 commits between tags, so I believe 1000 to be safe, but know 100 will not be.
We should continue to use
git describebecause it encodes both the most recent version and the exact commit past it where it's built.Resolves #2029.
Finding out right now from Travis CI if it's possible to completely disable shallow cloning.