Fix for handling dependabot force pushes. #98
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
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.
On a repository using the
path-filtering-orband dependabot, when a change occurs onmaindependabot will update it's open PR's by rebasing and force pushing.The
CIRCLE_SHA1that is then passed to the build contains a SHA that no longer exists (wiped out by the force push) and the checkout then fails with afatal: reference is not a tree: SHA.This slight change wraps the checkout in a try block and falls back on checking out
HEAD~1should that happen.NOTE: This will only really catch single commit force pushes. It's possible you could use
maininstead ofHEAD~1to handle more than 1 commit, but that would result in more things being built. This was a very specific edge case for working with dependabot.