Give a better message when Gemfile branch does not exist #6383
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
simi
approved these changes
Feb 15, 2023
simi
deleted the
improve-error-message-when-cloning-a-non-existent-branch
branch
deivid-rodriguez
pushed a commit
that referenced
this pull request
Mar 8, 2023
…ning-a-non-existent-branch Give a better message when Gemfile branch does not exist (cherry picked from commit 7abe7a6)
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.
What was the end-user or developer problem that led to this PR?
The error message when the branch in the Gemfile does not exist is too verbose, since the command is retried 3 times even if it will never succeed.
What is your fix for the problem, implemented in this PR?
Restore the good old Bundler 2.3 error.
This PR is analogous to #6356, but for non existent Gemfile branches.
Make sure the following tasks are checked