Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add build GitHub action #419

Merged
merged 1 commit into from
Mar 16, 2020
Merged

Add build GitHub action #419

merged 1 commit into from
Mar 16, 2020

Conversation

ashawley
Copy link
Collaborator

@ashawley
Copy link
Collaborator Author

This is the first installment of trying to solve #388.

@ashawley
Copy link
Collaborator Author

I suppose we could use the Jekyll action, but I'm pretty sure we need to have more control over the build than that going forward. Maybe the Jekyll action could be used to deploy the gh-pages.

@ashawley
Copy link
Collaborator Author

@ashawley
Copy link
Collaborator Author

I'll follow-up, and see if caching may be able to make this run slightly faster:

https://github.com/actions/cache/blob/master/examples.md#ruby---bundler

@ashawley ashawley merged commit 9c2508d into johno:master Mar 16, 2020
@ashawley ashawley deleted the gh-action branch March 16, 2020 14:26
@kosperera
Copy link

@ashawley I tried a combination of what you did for the build.yml script and another GitHub Action peaceiris/actions-gh-pages@v3. It seemed to do the job, at least for this repo:
https://github.com/kosalanuwan/bookworm/blob/master/.github/workflows/publish.yml

Notes:

  • The repo is a detached fork of Pixyll v2 and v3.
  • gh-pages only contains the _site binaries and not a copy of the master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants