Fallback to detecting latest revision if revisions-since call fails#124
Merged
ashwanthkumar merged 1 commit intoashwanthkumar:masterfrom Aug 2, 2018
Merged
Fallback to detecting latest revision if revisions-since call fails#124ashwanthkumar merged 1 commit intoashwanthkumar:masterfrom
ashwanthkumar merged 1 commit intoashwanthkumar:masterfrom
Conversation
This usually happens when an attempt is made to force-push, and in the meanwhile, the flyweight folder is deleted. The plugin tends to perform a `git log last-commit..HEAD` and the `last-commit` is no longer in the git object database, thereby rendering the plugin useless. A workaround is to ask that the old commit be force-pushed (hopefully whoever pushed the old commit still has it in their reflog)
Contributor
Author
|
I've taken the liberty to bump the revision number. Do you mind publishing a release when you get time? |
Owner
|
Thanks @ketan |
Owner
|
Published a new version v1.3.5 with these changes. |
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
2 participants
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.
This usually happens when an attempt is made to force-push, and in the
meanwhile, the flyweight folder is deleted. The plugin tends to perform
a
git log last-commit..HEADand thelast-commitis no longer in thegit object database, thereby rendering the plugin useless.
A workaround is to ask that the old commit be force-pushed (hopefully
whoever pushed the old commit still has it in their reflog)