Update scheduled workflow to use pages v4 #629
Merged
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.
Closes Homebrew/brew#17379
This PR modifies the scheduled regeneration workflow to mimic the one used for formulae.brew.sh.
I've removed the generated site files from
docs
and updated the.gitignore
file appropriately. If we want, we could rewrite the history of the repo to remove the generated files and make cloning take much less time (I can't remember whether we did that for formulae.brew.sh or not).The scheduled task now has three jobs:
generate
generates the site from Homebrew/brew, and also builds the site (i.e. runsbundle exec rake yard build
). I figured because there is only one generation task, there's no real benefit to splitting this up into a separategenerate
andbuild
job, but we can do that if we want to more closely mimic formulae.brew.shdeploy
deploys the site to GitHub pagesdeploy-issue
opens/closes deploy failure issues just like in formulae.brew.sh