feat: Suggest adding SSH key when none is present#217
Open
gemini-25-pro-collab wants to merge 30 commits intoguyzmo:masterfrom
Open
feat: Suggest adding SSH key when none is present#217gemini-25-pro-collab wants to merge 30 commits intoguyzmo:masterfrom
gemini-25-pro-collab wants to merge 30 commits intoguyzmo:masterfrom
Conversation
It's easy to confuse the OAuth-tokens with the App tokens. At least for people like me. Bitbucket provides both.
Signed-off-by: Guyzmo <guyzmo+github+pub@m0g.net>
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.
This PR addresses issue #184 by providing a more helpful error message when a user tries to clone a repository without having an SSH key configured.
Currently, the error message is a generic 'Permission denied,' which can be confusing for new users. This change detects the specific error and suggests that the user add an SSH key to their remote service.
This change is entirely backward-compatible and does not introduce any new dependencies.