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

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

Summary by CodeRabbit

Release Notes

• Chores
  • Internal maintenance updates to code ownership mappings.

---

Note: This release contains no user-facing changes.

[coderabbitai]

Walkthrough

The .github/CODEOWNERS file has been reorganized with codeowner mappings reassigned across multiple directories. Ownership updates span benchmarks/, flashinfer/*, include/, csrc/, docs/, ci-related paths, and trtllm/gemm entries, with members added, removed, and reordered.

Changes

Cohort / File(s)	Summary
Configuration Updates .github/CODEOWNERS	Reordered and reassigned codeowner mappings across multiple paths: benchmarks/ and benchmarks/routines/ ownership updated; flashinfer subdirectories reassigned to different owners; include/ and include/flashinfer/\* entries modified to reflect new owners with IwakuraRein and others added; trtllm/gemm and jit-related entries adjusted; csrc/, docs/, and ci-related paths reallocated.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Single file with repetitive, homogeneous changes across multiple paths
• Primarily reordering and reassignment of existing ownership patterns
• Main verification focus: confirm ownership assignments align with team structure and intent

Possibly related PRs

• PR #1984: Modifies the same .github/CODEOWNERS file with overlapping ownership reassignments for benchmarks, flashinfer subdirectories, include/, and csrc/ paths.
• PR #1949: Updates .github/CODEOWNERS with overlapping owner mappings and reordering across similar paths and directories.
• PR #2067: Makes overlapping ownership reassignments in .github/CODEOWNERS for benchmarks, csrc, include/flashinfer, and flashinfer/\* paths.

Suggested reviewers

• yzh119
• nvmbreughe
• bkryu
• yongwww

Poem

🐰 Through directories both great and small,
New owners claim their rightful hall,
With paths reordered, duties realigned,
Responsibilities freshly defined,
The warren's code now properly assigned! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: Update CODEOWNERS' clearly and concisely summarizes the main change—updating the CODEOWNERS file with maintenance focus.
Description check	✅ Passed	The PR description covers the essential sections: summary of changes, methodology (commit frequency, file coverage, recency), review instructions, and automation context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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

📝 Customizable high-level summaries are now available!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide custom instructions to shape the summary (bullet lists, tables, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example:

"Create a concise high-level summary as a bullet-point list. Then include a Markdown table showing lines added and removed by each contributing author."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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]

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 aims to maintain an accurate and up-to-date .github/CODEOWNERS file. By leveraging an automated process that analyzes recent commit history, it ensures that the designated code owners for various modules correctly reflect current contributions and expertise, thereby streamlining the code review process and improving team accountability.

Highlights

• Automated CODEOWNERS Update: The .github/CODEOWNERS file has been automatically updated based on an analysis of commit history from the last 180 days, considering commit frequency, file coverage, and commit recency.
• Ownership Reordering: Existing owners for several paths, including benchmarks/, benchmarks/routines/, flashinfer/fused_moe/, flashinfer/jit/, and include/flashinfer/gemm/, have been reordered to reflect updated contribution patterns.
• Owner Additions and Removals: Specific owners have been added or removed for various modules. For instance, @aleozlx was added to flashinfer/, flashinfer/fused_moe/, and flashinfer/jit/, while @IwakuraRein was added to include/ and include/flashinfer/. Conversely, some owners like @jiahanc and @wenscarl were removed or replaced in certain paths.

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

[gemini-code-assist]

Code Review

This pull request contains automated updates to the CODEOWNERS file based on recent git history. The changes appear to correctly reflect shifts in code contributions across different modules. My review identifies one area for improvement: a redundant entry where a subdirectory is assigned the same owners as its parent directory. This can be simplified by removing the redundant line.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4aed50c and 520dc2b.

📒 Files selected for processing (1)

• .github/CODEOWNERS (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Deploy Docs

🔇 Additional comments (1)

.github/CODEOWNERS (1)

6-7: Verify automated ownership assignments align with team structure.

Since this is an automated update based on commit history, ensure the reassigned owners accurately reflect current team responsibilities and include all critical stakeholders for each module. The automation may miss context such as recent team changes, planned handoffs, or domain expertise that isn't reflected in recent commit activity.

Also applies to: 20-20, 29-29, 31-31, 38-39, 42-43

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Remove duplicate username.

The username @Anerudhan appears twice in the owner list for flashinfer/cudnn/, which is redundant.

Apply this diff to remove the duplicate:

-flashinfer/cudnn/ @Anerudhan @yzh119 @cyx-6 @Anerudhan
+flashinfer/cudnn/ @Anerudhan @yzh119 @cyx-6

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	flashinfer/cudnn/ @Anerudhan @yzh119 @cyx-6 @Anerudhan
	flashinfer/cudnn/ @Anerudhan @yzh119 @cyx-6

🤖 Prompt for AI Agents

In .github/CODEOWNERS around line 26, the owners list for the path
flashinfer/cudnn/ contains a duplicated username (@Anerudhan); remove the
duplicate so each username appears only once (i.e., keep a single @Anerudhan and
leave the other owners unchanged).