Publish GitHub Pages upon successfully-merged PR #252
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
barroco
approved these changes
Oct 16, 2023
github-actions bot
added a commit
that referenced
this pull request
Oct 16, 2023
* Publish GitHub Pages upon successfully-merged PR * Exclude github_pages Markdown files from hygiene * Check out repo before running script * Specify checkout path * Attempt to fix artifact folder structure * Attempt to fix folder structure again 5742e0f
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.
This PR attempts to autogenerate a GitHub Pages site for this repository featuring (initially) a few of the artifacts generated during CI runs. The approach taken in this PR was generally tested on my personal GitHubPages repo, but I don't know how to effectively test whether it works prior to simply merging this PR.
When this PR is merged, I expect the new ci.yml job will be run when the other jobs complete successfully. The Deploy step should only be executed when committing/merging to the main branch. The result of successfully running the Deploy step is that a new gh-pages branch will be created on this repository and the generated site content will be committed to that branch. This repo does not yet have GitHub Pages enabled, so nothing more will happen initially. After this PR is successfully merged and the CI has successfully run and generated the gh-pages branch, I will enable GitHub pages by linking to the gh-pages branch. After doing that, the next commit/merge to main should cause the site content to actually be published.
Everything in the updated CI is running for the pull request except the final step of the new job (which writes to the gh-pages branch), so I expect this to work when merged.