Merge pull request #13629 from electron/use-dot-env

docs: use .env (and .env.example) for tokens used in release
This commit is contained in:
John Kleinschmidt 2018-07-17 11:57:42 -04:00 committed by GitHub
commit 05538aa32c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 23 additions and 12 deletions

View file

@ -8,11 +8,10 @@ upload an Electron release. Contact a team member for more
information.
There are a handful of `*_TOKEN` environment variables needed by the release
scripts. Once you've generated these per-user tokens, you may want to keep
them in a local file that you can `source` when starting a release.
scripts:
* `ELECTRON_GITHUB_TOKEN`:
Create as described at https://github.com/settings/tokens/new,
giving the token repo access scope.
Create this by visiting https://github.com/settings/tokens/new?scopes=repo
* `APPVEYOR_TOKEN`:
Create a token from https://windows-ci.electronjs.org/api-token
If you don't have an account, ask a team member to add you.
@ -26,6 +25,11 @@ with the scope of `Build (read and execute)`.
* `ELECTRON_S3_SECRET_KEY`:
If you don't have these, ask a team member to help you.
Once you've generated these tokens, put them in a `.env` file in the root directory
of the project. This file is gitignored, and will be loaded into the
environment by the release scripts.
## Determine which branch to release from
- **If releasing beta,** run the scripts below from `master`.