Commit 00c0fdd

committed

docs: note the potential requirement for user:email scope

Some GitHub Enterprise setups may require the additional `user:email` scope. Signed-off-by: Lucas Magasweran <lrm@linux.com>

1 parent ab14e27 commit 00c0fddCopy full SHA for 00c0fdd

File tree

-3

lines changed

-3

lines changed

Lines changed: 4 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -102,8 +102,9 @@ file.`
`102`	`102`	`#### Password-less login`
`103`	`103`
`104`	`104`	`If you have a complicated authorization requirement you can manually create a`
`105`		-token file by pasting a GitHub token with only the `gist` permission into a
`106`		-file called `~/.gist`. You can create one from https://github.com/settings/tokens
	`105`	+token file by pasting a GitHub token with `gist` scope (and maybe the `user:email`
	`106`	+for GitHub Enterprise) into a file called `~/.gist`. You can create one from
	`107`	`+https://github.com/settings/tokens`
`107`	`108`
`108`	`109`	`This file should contain only the token (~40 hex characters), and to make it`
`109`	`110`	easier to edit, can optionally have a final newline (`\n` or `\r\n`).
`@@ -156,7 +157,7 @@ If you need more advanced features you can also pass:`
`156`	`157`	* `:copy` to copy the resulting URL to the clipboard (default is false).
`157`	`158`	* `:open` to open the resulting URL in a browser (default is false).
`158`	`159`
`159`		`-NOTE: The access_token must have the "gist" scope.`
	`160`	+NOTE: The access_token must have the `gist` scope and may also require the `user:email` scope.
`160`	`161`
`161`	`162`	`‌If you want to upload multiple files in the same gist, you can:`
`162`	`163`

Comments

(0)