Skip to content

README update: Use umask when creating token file #303

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 2, 2019
Merged

README update: Use umask when creating token file #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,11 +106,13 @@ token file by pasting a GitHub token with only the `gist` permission into a
file called `~/.gist`. You can create one from https://github.com/settings/tokens

This file should contain only the token (~40 hex characters), and to make it
easier to edit, can optionally have a final newline (\n or \r\n).
easier to edit, can optionally have a final newline (`\n` or `\r\n`).

For example, one way to create this file would be to run:

echo MY_SECRET_TOKEN > ~/.gist
(umask 0077 && echo MY_SECRET_TOKEN > ~/.gist)

The `umask` ensures that the file is only accessible from your user account.

### GitHub Enterprise

Expand Down