Skip to content

Commit

Permalink
Gettext: Even more clarity (#17)
Browse files Browse the repository at this point in the history
  • Loading branch information
cassidyjames authored and danirabbit committed Nov 5, 2019
1 parent 56a35ac commit 279de6f
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion gettext-template/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,13 @@ This image is intended for use with elementary debian projects. There are a few

### Environment Variables

In order to create tags and push changes to various branches, the script needs a GitHub token. When using GitHub workflows, the virtual environment [automatically comes with a generated GitHub token secret](https://help.github.com/en/articles/virtual-environments-for-github-actions#github_token-secret). However, if your translation branch is protected, you will need to use a Personal Access Token with the `repo` scope, generated by a user who has admin permissions for the repo.
In order to create tags and push changes to various branches, the script needs a GitHub token. When using GitHub workflows, the virtual environment [automatically comes with a generated GitHub token secret](https://help.github.com/en/articles/virtual-environments-for-github-actions#github_token-secret). However, if your translation branch is protected, you will need to use a Personal Access Token with the `repo` scope, generated by a user who has admin permissions for the repo. To do so:

1. [Generate a Personal Access Token](https://github.com/settings/tokens/new) from your GitHub user settings
2. Give it the `repo` scope
3. Copy the generated Personal Access Token
4. In the repo's settings, navigate to the "Secrets" tab and "Add a new secret"
5. Name the new secret `GIT_USER_TOKEN` and paste the copied Personal Access Token

#### Git User

Expand Down

0 comments on commit 279de6f

Please sign in to comment.