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
docs: add troubleshooting page #1752
Conversation
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.
Left some suggestions.
docs/troubleshooting.md
Outdated
The easiest way to debug your `release-please` configuration is to use the bundled | ||
CLI. | ||
|
||
To use the CLI, you will need to use a GitHub personal access token: |
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.
I would link to creating a personal access token:
|
||
```bash | ||
export GITHUB_TOKEN="my-access-token" | ||
release-please release-pr \ |
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.
Since many folks using the tool are non JavaScript users, I would add a section on:
"Setting up your environment", which links to nvm and explains they will need to:
- git clone the repository.
- setup Node.js with nvm.
- npm i
- npm link .
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.
I don't think it's necessary to teach folks how to install node.
Fixes #1687