Sync upstream: docs assistant integration (#1730)#8
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.
Manual sync of
upstream/master→parity-deploy, bringing the docs assistant integration (polkadot-developers#1730).The scheduled
sync-upstreamjob can't do this one automatically, for two reasons:requirements.txtconflict — upstream added a note on thepapermoon-mkdocs-pluginsline; we install it from our own fork. Resolved here by keeping our fork line..github/workflows/*, which the Actions bot can't push withoutworkflowspermission. That's why this needs a human-merged PR.Merging this publishes the site with the chat widget live —
DOCS_ASSISTANT_API_URLis already set as a repo variable.Follow-up (not this PR): give
sync-upstream.ymlaworkflow-scoped token so future workflow-touching syncs don't need a manual PR.