development/github-desktop
development/github-desktop
1
0
Fork 0
mirror of https://github.com/desktop/desktop synced 2024-09-13 21:31:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

group the instructions per shell, not per-OS

Browse source
This commit is contained in:
Brendan Forster 2018-03-15 11:09:51 +11:00 committed by GitHub
parent e04a560ec8
commit 43e48f9c76
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
docs/process/releasing-updates.md
View file

@ -16,12 +16,19 @@ We have three channels to which we can release: `production`, `beta`, and `test`
From a clean working directory, set the `GITHUB_ACCESS_TOKEN` environment variable to a valid [Personal Access Token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) From a clean working directory, set the `GITHUB_ACCESS_TOKEN` environment variable to a valid [Personal Access Token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/)
You can check that this is set on macOS or via Git Bash (Windows) by: To check that this environment variable is set in your shell:
**Bash (macOS, Linux or Git Bash)**
```shellsession ```shellsession
$ echo $GITHUB_ACCESS_TOKEN $ echo $GITHUB_ACCESS_TOKEN
``` ```
You can check that this is set on Windows (PowerShell) by: **Command Prompt**
```shellsession
$ echo %GITHUB_ACCESS_TOKEN%
```
**PowerShell**
```shellsession ```shellsession
$ echo $env:GITHUB_ACCESS_TOKEN $ echo $env:GITHUB_ACCESS_TOKEN
``` ```
@ -30,16 +37,23 @@ If you are creating a new Personal Access Token on GitHub:
* make the token memorable - use a description like `Desktop Draft Release and Changelog Generator` * make the token memorable - use a description like `Desktop Draft Release and Changelog Generator`
* the `read:org` scope is the **only** required scope for drafting releases * the `read:org` scope is the **only** required scope for drafting releases
You can add an access token as an environment variable on macOS by: To set this access token as an environment in your shell:
**Bash (macOS, Linux or Git Bash)**
```shellsession ```shellsession
$ export GITHUB_ACCESS_TOKEN={your token here} $ export GITHUB_ACCESS_TOKEN={your token here}
``` ```
You can add an access token as an environment variable on Windows by: **Command Prompt**
```shellsession ```shellsession
$ set GITHUB_ACCESS_TOKEN={your token here} $ set GITHUB_ACCESS_TOKEN={your token here}
``` ```
**PowerShell**
```shellsession
$ $env:GITHUB_ACCESS_TOKEN="{your token here}"
```
### 2. Create Draft Release ### 2. Create Draft Release
Once the personal access token is set, run the script below, which will determine the next version from what was previously published, based on the desired channel. Once the personal access token is set, run the script below, which will determine the next version from what was previously published, based on the desired channel.