chore: Update CODEOWNERS

[flashinfer-bot]

Summary

This PR updates the CODEOWNERS file based on git commit history analysis from the last 180 days.

Changes

• Updated .github/CODEOWNERS with current code ownership based on:
  • Commit frequency
  • File coverage
  • Commit recency
  • Manual overrides from scripts/codeowner_overrides.json

How to Review

1. Review the changes to .github/CODEOWNERS
2. Verify that the assigned owners are appropriate for each module
3. Make manual adjustments if needed before merging

Notes

• This is an automated PR generated weekly
• Minimum commits threshold: 1
• Analysis period: 180 days
• Directory depth: 3 levels
• Top N owners per module: 5

---

🤖 This PR was automatically generated by the update-codeowners workflow

[gemini-code-assist]

Summary of Changes

Hello @flashinfer-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request ensures that the project's code ownership is accurately reflected in the .github/CODEOWNERS file. By automating this process weekly, it maintains up-to-date assignments based on recent development activity, streamlining code review assignments and ensuring accountability.

Highlights

• Automated CODEOWNERS Update: This pull request automatically updates the .github/CODEOWNERS file based on a recent analysis of commit history over the last 180 days.
• Ownership Criteria: The ownership analysis considers factors such as commit frequency, file coverage, and commit recency to determine the most appropriate code owners for each module.
• Minor Reordering: The specific change in this PR involves a minor reordering of two owners for the include/flashinfer/trtllm/ path, reflecting updated ownership based on the analysis.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

📝 Walkthrough

Walkthrough

Rewrites .github/CODEOWNERS with broad reallocation and expansion of ownership mappings: adds a top-level manual-override and numerous per-directory and per-file owner assignments across benchmarks, ci, csrc, flashinfer, include, docs, scripts, and tests. No code or API signatures changed.

Changes

Cohort / File(s)	Summary
Primary CODEOWNERS ​.github/CODEOWNERS	Top-level manual-override added; large-scale reordering, additions, removals and many explicit per-file ownership overrides.
Benchmarks & CI benchmarks/..., benchmarks/routines/..., ci/...	Reassigned and reordered owners for benchmark and CI paths with new group additions.
C++ sources (csrc) csrc/..., csrc/fmha_v2/..., csrc/fused_moe/...	Ownership reassignments across csrc, including fmha_v2 and fused_moe subpaths; many directory-level changes.
FlashInfer modules flashinfer/..., flashinfer/comm/..., flashinfer/jit/..., flashinfer/fused_moe/...	Moved and replaced owner groups for flashinfer root and subdirectories; file-level overrides added.
Public headers & include/ include/..., include/flashinfer/...	Header ownership lists adjusted with new include/flashinfer-specific owners and per-file mappings.
Docs & Scripts docs/..., scripts/...	Docs and scripts owner lists modified and reordered.
Tests & misc top-level paths tests/..., nv_internal/..., other top-level paths	Test-suite and nv_internal ownership entries updated; explicit path-specific overrides added.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• chore: Update CODEOWNERS #2135 — overlapping edits to .github/CODEOWNERS, reassigning and adding owners across similar repo paths.
• chore: Update CODEOWNERS #2067 — prior substantial updates to CODEOWNERS affecting benchmarks, csrc, flashinfer, include, and tests.
• infra: add manual code owner override support in codeowner_analyzer.py #2418 — introduced support for manual owner overrides/codeowner_overrides mechanism referenced by new override entries.

Suggested reviewers

• nvmbreughe
• kahyunnam
• yzh119
• jimmyzho

Poem

🐰 I tweaked the lists with a careful hop,
Names shifted softly—no code went pop.
Paths got new keepers, lines rearranged,
My whiskers twitched while ownerships changed.
I hop away, the repo neat on top.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description includes a summary, detailed changes, review instructions, and notes about the automated process. However, it does not follow the provided template structure with required sections like 'Related Issues', 'Pre-commit Checks', or 'Tests'.	Consider following the repository's pull request template structure with sections for Related Issues, Pre-commit Checks, and Tests, even for automated chore PRs.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: Update CODEOWNERS' is clear and directly describes the main change in the PR—updating the CODEOWNERS configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch auto-update-codeowners

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[gemini-code-assist]

Code Review

This pull request contains an automated update to the .github/CODEOWNERS file. The change reorders two owners for the include/flashinfer/trtllm/ path, which aligns with the PR's goal of reflecting recent contribution history. The change is syntactically correct and appears to be functioning as intended by the automation script. I have reviewed the change and found no issues.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/CODEOWNERS:
- Line 49: The CODEOWNERS entry for the "scripts/" path contains a duplicate
owner (`@yongwww`); edit the "scripts/ `@yzh119` `@yongwww` `@nvmbreughe` `@kahyunnam`
`@yongwww`" line to remove the repeated `@yongwww` so each owner appears only once
(e.g., "scripts/ `@yzh119` `@yongwww` `@nvmbreughe` `@kahyunnam`").

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/CODEOWNERS:
- Line 47: Update the CODEOWNERS entry for the path "include/flashinfer/mamba/"
to list the actual contributors instead of only `@yzh119`: modify the line
"include/flashinfer/mamba/ `@yzh119`" to include Igor Shovkun and Zihao Ye (their
GitHub handles) alongside any existing owner(s) so the entry reflects the commit
history and current maintainers; ensure the format remains a single
space-separated list of owners after the path.