fix(linter): prevent category rules from being reapplied to already-configured plugins in overrides

[camc314]

fixes #12859

[camc314]

• fix(linter): prevent category rules from being reapplied to already-configured plugins in overrides #12875 👈 (View in Graphite)
• main

---

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.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12875 will not alter performance

_{Comparing c/08-07-fix_linter_prevent_category_rules_from_being_reapplied_to_already-configured_plugins_in_overrides (6b4a7a7) with main (306b023)¹}

Summary

✅ 34 untouched benchmarks

Footnotes

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

[camc314]

Ecosystem CI running here > https://github.com/oxc-project/oxlint-ecosystem-ci/actions/runs/16805621676

looks OK

[camc314]

Merge activity

• Aug 7, 1:53 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Aug 7, 1:53 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Aug 7, 1:56 PM UTC: Merged by the Graphite merge queue.

[Boshen]

I still want a post-review from @camchenry, if you are willing and have the time.

[camchenry]

@Boshen @camc314 Looks okay to me. I'm a bit rusty on the config resolution logic, but I can't think of a better solution at the moment. The whole config system probably needs a refactor at some point, but at least this gives us another good test case to prevent regressions.