Skip to content
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

Clarify documentation on the required GitHub access token #147

Open
datenreisender opened this issue Apr 26, 2018 · 1 comment
Open

Clarify documentation on the required GitHub access token #147

datenreisender opened this issue Apr 26, 2018 · 1 comment

Comments

@datenreisender
Copy link

In https://github.com/greenkeeperio/greenkeeper-lockfile/blame/master/README.md#L41 it says:

First create a GitHub access token with push access to your repository and make it available to your CI's environment as GH_TOKEN.

This left me unsure about which scope I should choose on https://github.com/settings/tokens/new to allowgreenkeeper-lockfile to push to my private repo. I assume repo is necessary and sufficient.

If this is correct, it would be helpful, to state this more clearly in the docs.

@jonathanong
Copy link

could we just use SSH instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants