Repository navigation
Indent dag-run span TODO comment continuation lines - #68643
Merged
dstandish merged 1 commit intoJun 18, 2026
Merged
Conversation
Indent the continuation lines of the _emit_dagrun_span TODO comment by one extra space and add a blank line before it, so JetBrains/PyCharm highlights the whole TODO block. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ashb
approved these changes
Jun 18, 2026
ashb
left a comment
Member
There was a problem hiding this comment.
As long a linters are happy with this sure whatever :)
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.
Comment-only change: indent the continuation lines of the
_emit_dagrun_spanTODO comment by one extra space and add a blank line before it, so JetBrains/PyCharm highlights the whole TODO block (its TODO highlighting expects continuation lines to be indented under the# TODO:marker).Split out of #68591 to keep that PR focused.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines