DOC Sync six drifting Jupytext notebook pairs - #2449
Merged
Roman Lutz (romanlutz) merged 2 commits intoAug 22, 2026
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
hannahwestra25
approved these changes
Aug 21, 2026
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.
Description
Six documentation notebooks had drifted from their paired Jupytext percent files. This made code cells inconsistent between rendered notebooks and reviewable Python sources, including missing markdown cell separators and imports in the WebSocket Copilot target example.
Synchronize each pair from its authoritative content while preserving existing notebook outputs and metadata. The WebSocket and Playwright pairs merge the valid imports and cell boundaries from both representations; the remaining pairs align wording or remove stray code-cell whitespace. Jupytext-equivalent metadata differences outside these six pairs are intentionally left unchanged to avoid generated churn.
Tests and Documentation
uv run jupytext --diffaudit to identify the six drifting pairs.uv run jupytext --diff <file.py> <file.ipynb>produces no diff for every affected pair.uv run ruff checkanduv run ruff format --checkon the changed percent files.git diff --check.