Let the Pages deployment create the site it publishes to - #4
Merged
Conversation
The first run after merging failed in configure-pages: the repository has no Pages site, and the step looks for one rather than creating it. Nothing about the page itself was wrong. Asking the step to create the site keeps the workflow self-contained instead of depending on a setting someone has to remember to flip, and it does nothing once the site exists. It still needs the workflow token to be allowed to create one, so if this run fails the same way, the setting is the only route: Settings, Pages, source GitHub Actions.
This file contains hidden or 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
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.
The first deploy after merging #2 failed in
actions/configure-pages:The repository has no Pages site yet, and the step looks for one rather than
creating it. The landing page itself is fine.
This sets
enablement: trueso the workflow creates the site on its first runand is a no-op afterwards.
This may not be sufficient on its own. Creating a Pages site needs the
workflow token to be permitted to do it. If the re-run fails the same way, an
administrator has to flip the setting once instead: Settings → Pages → Build and
deployment → Source: GitHub Actions, then re-run the workflow. I don't have
admin on this repository, so I can't do that or test it from here.