Run pyink on files that landed unformatted (PRs #436, #438)#441
Merged
copybara-service[bot] merged 1 commit intoJul 8, 2026
Merged
Conversation
entrpn
approved these changes
Jul 8, 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
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.
Summary
Format-only change: runs
pyink==23.10.0(the CI's exact version and flags:--pyink-indentation=2 --line-length=125) over 5 files that landed on main unformatted.On PRs #436 and #438 the
AddPullReadybot failed (fork-PR token permissions); the label was added manually, which does not re-trigger the test workflow, so the CPU-tests job (pylint + pyink) never ran and both PRs merged without the repo-wide format gate. The first PR to run CI afterwards (#437) now fails the pyink check on these files.Unblocks #437 (rebase after merge).