Repository navigation
docs(site): build when the last deploy's commit is missing from the shallow clone - #54
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
🎉 This PR is included in version 0.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This branch was successfully deployed
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
1 participant
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.
Vercel's ignore step ran
git diffagainstVERCEL_GIT_PREVIOUS_SHA. When that commit isn't in the shallow clone (staging had moved 16 commits since the last deploy),git diffexits 128. Vercel treats any exit code other than 0 (skip) or 1 (build) as a failed deployment, which is the Vercel failure on #53.The step now checks that the commit exists first. A missing commit or any other error means build. A commit that is present still skips the build when nothing under the site, packages or lockfile changed.
Tested locally: a commit missing from the clone used to exit 128 and now exits 1 (build). The current HEAD exits 0 (skip), and an older commit with site changes exits 1.