Skip to content

Commit

Permalink
SETUP: wording tweaks (#366)
Browse files Browse the repository at this point in the history
merges manubot/rootstock#366

clarifies that
1. OWNER can be an organization!
2. no additional configuration is needed for github actions.
  • Loading branch information
ctb authored Sep 30, 2020
1 parent 0964fd7 commit 15db623
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions SETUP.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ In general, assume that all commands in this setup are case-sensitive.
**Edit the following commands with your manuscript's information:**

```sh
# GitHub username (change from manubot)
# GitHub username or organization name (change from manubot)
OWNER=manubot
# Repository name (change from rootstock)
REPO=rootstock
Expand Down Expand Up @@ -115,7 +115,7 @@ git rm .appveyor.yml
git rm ci/install.sh
```

GitHub Actions is _usually_ able to deploy without any setup using the [`GITHUB_TOKEN`](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token) for authentication.
GitHub Actions is _usually_ able to deploy without any additional setup using the [`GITHUB_TOKEN`](https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token) for authentication.
GitHub Pages deployment using `GITHUB_TOKEN` recently started working on GitHub without an official announcement.
If it does not work for you after completing this setup, try reselecting "gh-pages branch" as the Source for GitHub Pages in the repository Settings.
GitHub Pages should now trigger on the next commit.
Expand Down

0 comments on commit 15db623

Please sign in to comment.