Repository navigation
Format all Python files with ruff (format-only) - #19
Open
OlgaPushkarev wants to merge 1 commit into
Open
OlgaPushkarev wants to merge 1 commit into
OlgaPushkarev wants to merge 1 commit into
Conversation
Applies 'ruff format' (default black-compatible style, line length 88) to every tracked .py file so later changes have small, reviewable diffs. Notebooks are untouched. After this is merged, its commit should be added to .git-blame-ignore-revs so git blame skips it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 10, 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.
Summary
Applies
ruff format(default black-compatible style, line length 88) to every tracked.pyfile, so later changes have small, reviewable diffs. Format-only: no behavior change, and notebooks are untouched.Second of three stacked PRs. It is based on the lab-content cleanup PR (#18); #20 builds on this one. After that one merges, GitHub retargets this PR to
main.Verification
ast.dumpcomparison of all 136 changed files before and after: identical, except docstring whitespace normalization in 17 files..pyfiles compile, andruff format --checkpasses on the whole repo.After merging
Add the merged commit's SHA to a new
.git-blame-ignore-revsfile, sogit blameskips this commit; GitHub reads that file automatically. The SHA is only known after a squash merge, so this is done in a follow-up.🤖 Generated with Claude Code