-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
ci(linter): skip linter benchmarks on unrelated file changes #6705
ci(linter): skip linter benchmarks on unrelated file changes #6705
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
48b22e1
to
20633ec
Compare
CodSpeed Performance ReportMerging #6705 will not alter performanceComparing Summary
|
This is a really good idea. The linter benchmarks are always the slowest to complete. I'm not familiar with
And not:
It's possible a PR might make changes to both the linter and the transformer, and we'd want linter benchmarks to run in that case. |
I believe so. I followed the example in |
Skip building/running linter benchmarks on PRs that only change the transformer, ID, formatter, or the minifier.