Skip to content

feat(linter/fixer): expose find_next_token_from in fixer#17940

Merged
graphite-app[bot] merged 1 commit intomainfrom
c/01-12-feat_linter_fixer_expose_find_next_token_from_in_fixer
Jan 12, 2026
Merged

feat(linter/fixer): expose find_next_token_from in fixer#17940
graphite-app[bot] merged 1 commit intomainfrom
c/01-12-feat_linter_fixer_expose_find_next_token_from_in_fixer

Conversation

@camc314
Copy link
Contributor

@camc314 camc314 commented Jan 12, 2026

No description provided.

@camc314 camc314 marked this pull request as ready for review January 12, 2026 21:31
Copilot AI review requested due to automatic review settings January 12, 2026 21:31
@github-actions github-actions bot added the A-linter Area - Linter label Jan 12, 2026
Copy link
Contributor Author

camc314 commented Jan 12, 2026


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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 github-actions bot added the C-enhancement Category - New feature or request label Jan 12, 2026
@camc314 camc314 self-assigned this Jan 12, 2026
@graphite-app
Copy link
Contributor

graphite-app bot commented Jan 12, 2026

Merge activity

@codspeed-hq
Copy link

codspeed-hq bot commented Jan 12, 2026

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing c/01-12-feat_linter_fixer_expose_find_next_token_from_in_fixer (f04aa60) with main (63e2737)1

Summary

✅ 4 untouched benchmarks
⏩ 41 skipped benchmarks2

Footnotes

  1. No successful run was found on main (f04aa60) during the generation of this report, so 63e2737 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@graphite-app graphite-app bot force-pushed the c/01-12-feat_linter_fixer_expose_find_next_token_from_in_fixer branch from 9603cd6 to f04aa60 Compare January 12, 2026 21:37
@graphite-app graphite-app bot merged commit f04aa60 into main Jan 12, 2026
20 checks passed
@graphite-app graphite-app bot deleted the c/01-12-feat_linter_fixer_expose_find_next_token_from_in_fixer branch January 12, 2026 21:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter C-enhancement Category - New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant