Git remote repository access. Currently, shepherd just expects command like git clone to work in the current environment (e.g., your ssh key is set up).
This information should be documented and the tutorial should mention how to set things up if you haven't already.
We could also better handle the failure cases when auth is not available and print helpful error message.
Currently there's two types of auth needed to use shepherd:
GitHub API auth. Currently, api auth can come from either a
GITHUB_TOKEN
environment variable or a~/.netrc
file. See code: https://github.com/NerdWalletOSS/shepherd/blob/40f4272c883a2465e8e927ea29293900be928e63/src/adapters/github.ts#L36-L49Git remote repository access. Currently, shepherd just expects command like
git clone
to work in the current environment (e.g., your ssh key is set up).This information should be documented and the tutorial should mention how to set things up if you haven't already.
We could also better handle the failure cases when auth is not available and print helpful error message.