Fix the update-gh-pages-documentation-site script so that it publishes the new documentation
#1365
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
…ntation gets published
d-ronnqvist
commented
Nov 28, 2025
| --output-path "$DOCC_UTILITIES_OUTPUT_DIR" | ||
|
|
||
| echo -e "\033[34;1m Merging docs \033q[0m" | ||
| echo -e "\033[34;1m Merging docs \033[0m" |
Contributor
Author
There was a problem hiding this comment.
Because this wasn't a valid ANSI Escape Code before, the rest of the output from this script was in blue, as opposed to just this message which is what was intended.
heckj
approved these changes
Nov 29, 2025
Contributor
Author
|
@swift-ci please test |
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.
Bug/issue #, if applicable:
Summary
This updated the
bin/update-gh-pages-documentation-sitescript so that it adds '.nojekyll' file in the 'docs' output. Without it, our prebuilt documentation won't be published.Dependencies
None
Testing
It's hard to test this without updating the live documentation. If you have access, you can see in the deployments that I've been able to make new documentation deployments.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
./bin/testscript and it succeeded