Update CODEOWNERS

[vrubezhny]

Add @vrubezhny to CODEOWNERS

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 0dc90077-a180-4bb0-8fab-2fb9aea4df0b

📥 Commits

Reviewing files that changed from the base of the PR and between d980f73 and 75b6e1e.

📒 Files selected for processing (1)

• .github/CODEOWNERS

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated code ownership configuration.

Walkthrough

The CODEOWNERS file was updated to add a new team member, @vrubezhny, to the default owners list for all repository files (the * rule). This is a straightforward configuration change adding ownership coverage.

Changes

Ownership Configuration

Layer / File(s)	Summary
Default owner assignment .github/CODEOWNERS	The * default owners rule was modified to add @vrubezhny to the existing set of code owners.

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Update CODEOWNERS' accurately summarizes the main change of adding a team member to the CODEOWNERS file.
Description check	✅ Passed	The description 'Add @vrubezhny to CODEOWNERS' is directly related to the changeset and clearly describes the specific change being made.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.1.0
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions