-
-
Notifications
You must be signed in to change notification settings - Fork 721
refactor(linter): use fast-glob instead of globset for GlobSet
#12870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(linter): use fast-glob instead of globset for GlobSet
#12870
Conversation
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. |
fast-glob instead of globset for GlobSet
5d2565d to
9adf236
Compare
CodSpeed Instrumentation Performance ReportMerging #12870 will not alter performanceComparing Summary
Footnotes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shulaoda is there any risk to any changes to how patterns are matched, when switching from globset to fast-glob.
e.g. are there any cases where a pattern would previously match, but now does not match correctly (or the reverse)
In general, the syntax of |
|
Additionally, for patterns like |
9adf236 to
63ba7de
Compare
Merge activity
|
63ba7de to
238b183
Compare

closes #12825