fix(ci): extend Pages deployment timeout#122
Merged
Merged
Conversation
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
2 participants
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.
What & why
Extends the GitHub Pages deployment wait from the action default of 10 minutes to 30 minutes.
The game-dump deployment built and uploaded a 212MB Pages artifact successfully, then remained in
syncing_filesuntilactions/deploy-pages@v4cancelled it at its 600,000ms default. The large static record count needs more time for the Pages service to synchronize.Source
GitHub's
actions/deploy-pagesaction documents a 600,000ms default timeout and supports overriding it through thetimeoutinput.Checklist
.github/workflows/deploy-pages.ymlis changed