Show possible locations when specifying non-existant paths in github CLI integration#5068
Open
Flamefire wants to merge 1 commit intoeasybuilders:developfrom
Open
Show possible locations when specifying non-existant paths in github CLI integration#5068Flamefire wants to merge 1 commit intoeasybuilders:developfrom
Flamefire wants to merge 1 commit intoeasybuilders:developfrom
Conversation
7da7b2b to
f00adea
Compare
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
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.
(created using
eb --new-pr)This adds a 2nd line to the existing error:
However I don't like having to specify the full paths to easyconfigs in my dev tree/search-path when EB can and does already resolve them.
Shall we enhance it like:
If easyconfig is found and not ambiguous (could that even happen? Can't see how) then use its path (instead of showing its location)