chore(linter): add statement_span to ExportEntry
#9441
Merged
+4
−0
Conversation
This file contains 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
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
github-actions
bot
added
A-linter
Sysix
commented
Feb 28, 2025
CodSpeed Performance ReportMerging #9441 will not alter performanceComparing Summary
|
Sysix
force-pushed
the
02-28-docs_linter_add_full_documentation_to_rule_no-restricted-imports_
branch
from
47eef53 to
5673ded
Compare
Sysix
force-pushed
the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
from
481df53 to
ec32386
Compare
Sysix
force-pushed
the
02-28-docs_linter_add_full_documentation_to_rule_no-restricted-imports_
branch
from
5673ded to
73a01e3
Compare
Sysix
force-pushed
the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
from
ec32386 to
27929e6
Compare
Sysix
changed the base branch from
02-28-docs_linter_add_full_documentation_to_rule_no-restricted-imports_
to
graphite-base/9441
Sysix
force-pushed
the
graphite-base/9441
branch
from
73a01e3 to
d43b456
Compare
Sysix
force-pushed
the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
from
27929e6 to
350aa23
Compare
Sysix
force-pushed
the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
from
350aa23 to
22e23c0
Compare
Merge activity
|
graphite-app
bot
force-pushed
the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
from
22e23c0 to
6440e5e
Compare
graphite-app
bot
deleted the
02-28-chore_linter_add_statement_span_to_exportentry_
branch
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.
No description provided.