-
Notifications
You must be signed in to change notification settings - Fork 2
Adding an SSH troubleshooting note to README #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Conversation
Clarify the SSH key error in the README
WalkthroughThe README file's troubleshooting section was updated to address the Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
README.md (1)
112-115: Consider adding the HTTPS clone command as a quick CLI fallbackThe new GitHub Desktop hint is helpful, but many developers will still prefer a pure-terminal workflow. A one-liner such as
git clone https://github.com/a8cteam51/team51-cli.gitworks without SSH keys and doesn’t require Desktop. Mentioning it here would round out the troubleshooting advice and keep users in the same context as the rest of the installation steps.
I kept running into the
Permission denied (publickey)error when trying to clone the repo. I'm not sure if the process is slightly different for full-timers, but as a contractor, I didn't receive the "AutoProxy passphrase" mentioned in the installation guide. The only thing that worked for me was cloning the repo via GitHub Desktop, which handled the authentication automatically.This PR adds a note to the README with a suggestion to use GitHub Desktop as a workaround. :)
Summary by CodeRabbit
[email protected]: Permission denied (publickey)error by suggesting the use of GitHub Desktop for cloning repositories.