Skip to content

Commit

Permalink
Merge pull request #1 from skohub-io/minorFixes
Browse files Browse the repository at this point in the history
Fix typo and improve formatting
  • Loading branch information
sroertgen authored Nov 9, 2020
2 parents adad1dc + bab7cd8 commit 7102796
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/main.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Build /public and delpoy to gh-pages with docker container
name: Build /public and deploy to gh-pages with docker container

on:
push:
Expand Down
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,8 @@ If you want to reuse this repo and have your vocabulary automatically pushed und
1. Fork this repo

2. go to the `.github/workflows/main.yml`-file, make sure to replace the following lines:

- line 34: `run: git clone https://github.com/skohub-io/skohub-docker-vocabs.git data/` <- adjust the path to point to **YOUR** repository
- line 37: `run: echo "PATH_PREFIX=/skohub-docker-vocabs" > .env.production` <- the `PATH_PREFIX` has to be set to **YOUR** repository name (only necessary if you changed the repository name; if you just forked and did not rename, leave it as it is)
- line 34: `run: git clone https://github.com/skohub-io/skohub-docker-vocabs.git data/` <- adjust the path to point to **YOUR** repository
- line 37: `run: echo "PATH_PREFIX=/skohub-docker-vocabs" > .env.production` <- the `PATH_PREFIX` has to be set to **YOUR** repository name (only necessary if you changed the repository name; if you just forked and did not rename, leave it as it is)

3. in your repository settings go to the "GitHub Pages" setting and select `gh-pages` as the branch your site is being built from. If it is not available yet, you might have to push something to your repo, so the GitHub-Action gets triggered or you can trigger it manually with going to "Actions" in the menubar, then select the workflow "Build /public and deploy..." and click "Run workflow". This way you can trigger the workflow automatically.

Expand Down

0 comments on commit 7102796

Please sign in to comment.