[Backport release v1] Comment on PR when target branch not found #311
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
When the target cannot be found on remote, then the git fetch fails with: (example for `maintenance/8.1`) ``` fatal: couldn't find remote ref maintenance/8.1 'git fetch origin maintenance/8.1' failed with exit code 128 ``` We can improve this by throwing a special error and handling it explicitly by commenting on the original pull request about this situation. We can also help the user figure out how to resolve the problem by making it clear that a branch with that name should exist. (cherry picked from commit f16f704)
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.
Manual backport to
release-v1ofManually created because of: