Your org has enabled the Graphite merge queue for merging into main

Add 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.

• feat(linter): output rules to json array #7574 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

thanks you @camc314 ❤️

I also tried to implement it today and found some problems on the way.
For the moment this looks great 👍

For the future I would like to have an OutputFormatter interface.
Then maybe we can handle all the use cases for the different --format options and other flag combinations

CodSpeed Performance Report

Merging #7574 will not alter performance

_{Comparing c/12-01-feat_linter_output_rules_to_json_array (275d625) with main (4e3044e)}

Summary

✅ 30 untouched benchmarks

Merge activity

• Dec 1, 10:13 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 1, 10:13 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 1, 10:26 PM EST: A user merged this pull request with the Graphite merge queue.

@Sysix Feel free to add more meta data for your requirements.