Update documentation build to use "assets" #316
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hiker
approved these changes
Jun 24, 2024
|
@MatthewHambley , could you please fix the conflicts, then I'm happy to merge. |
yaswant
reviewed
Jul 1, 2024
| on: | ||
| push: | ||
| branches: | ||
| - 'main' |
There was a problem hiding this comment.
This workflow targets main, but there is not such a branch - Perhaps Master needs renaming as main?
There was a problem hiding this comment.
Thanks, I've opened #321 for this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub have changed the way they handle "pages."
In the past they were taken from a branch in the repository called "gh_pages." Now they are tarred up as an "asset" and installed from there.
This change reflects that.
I've tested it as far as I can but it's always hard to be certain if workflows are correct until they are deployed.