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

• Chores
  • Updated code ownership and review assignments across project directories to optimize approval workflows and access control management.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The .github/CODEOWNERS file is updated with ownership reassignments and modifications across multiple project paths, including directories for docs, flashinfer, include, and trtllm. Owner groups are added, removed, or reordered, affecting approval permissions and code review assignments without altering any functional code.

Changes

Cohort / File(s)	Summary
CODEOWNERS Updates \.github/CODEOWNERS	Updated owner group assignments and reassignments across docs, flashinfer, include, and trtllm paths; added and removed owner entries (including kahyunnam and nv-yunzheq); reordered ownership mappings.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Single file modification with pure metadata/ownership updates
• No logic changes or runtime behavior impact
• Straightforward verification of ownership assignments against intended team structure

Possibly related PRs

• #1984: Modifies identical .github/CODEOWNERS entries with overlapping ownership reassignments and reorderings.
• #1949: Makes overlapping edits to the same CODEOWNERS file, updating ownership mappings for many of the same paths.
• #2067: Performs overlapping ownership updates across the same CODEOWNERS paths with owner group replacements and reassignments.

Suggested reviewers

• yzh119
• nvmbreughe
• bkryu

Poem

🐰 With whiskers twitched and paws aligned,
We shuffle owners, reassigned!
From docs to flashinfer we roam,
Each path now has a rightful home. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description provides good context about the purpose, methodology, and review guidance, though it doesn't follow the provided template structure with sections like '📌 Description', '🔍 Related Issues', and '🚀 Pull Request Checklist'.	Consider following the repository's PR template by organizing content under the standard sections (Description, Related Issues, Checklist) to ensure consistency and clarity for reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: Update CODEOWNERS' is clear and directly describes the main change, which is updating the CODEOWNERS file.
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 in beta!

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

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

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 serves to maintain an accurate and current .github/CODEOWNERS file. By automating the update process based on recent commit history, it ensures that the designated owners for various code paths are correctly assigned, streamlining review processes and clarifying responsibilities across the codebase.

Highlights

• CODEOWNERS Update: The .github/CODEOWNERS file has been automatically updated to reflect current code ownership based on recent commit history analysis.
• Automated Process: This pull request is generated weekly by an automated workflow, ensuring that code ownership remains accurate and up-to-date.
• Ownership Criteria: Ownership assignments are determined by commit frequency, file coverage, and commit recency over the last 180 days, with a minimum commit threshold of 1, a directory depth of 3 levels, and up to 5 top owners per module.

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 PR updates the CODEOWNERS file based on an automated analysis of the git history. The changes seem mostly correct, reflecting recent contributions. However, I've found an issue where a user is listed as an owner twice for the same path, which should be corrected. This is likely due to a bug in the generation script that doesn't handle multiple email addresses for the same GitHub user correctly. While a manual fix is possible for this PR as suggested in the PR description, the underlying script should be updated to prevent this from happening in the future.

[gemini-code-assist]

The user @Anerudhan is listed twice as an owner for this path. The list of owners for a path should not contain duplicates. Please remove the duplicate entry.

It's likely that the script that generated this file (scripts/codeowner_analyzer.py) has a bug where it treats contributions from the same person using different emails as separate contributors, leading to this duplication. It would be best to fix the script to avoid this issue in future automated PRs.

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

[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 cf2df82 and 65f25f3.

📒 Files selected for processing (1)

• .github/CODEOWNERS (1 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

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Remove duplicate owner.

@Anerudhan is listed twice on this line, which indicates a bug in the automation script that generated this file. While GitHub will deduplicate this automatically, it should be corrected for clean configuration.

Apply this diff to remove the duplicate:

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

Additionally, consider investigating and fixing the automation script to prevent similar duplicates in future updates.

📝 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 @bkryu @cyx-6 @Anerudhan
	flashinfer/cudnn/ @Anerudhan @yzh119 @bkryu @cyx-6

🤖 Prompt for AI Agents

.github/CODEOWNERS around line 26: the owners list contains a duplicate entry
"@Anerudhan" on the same line; remove the duplicate so the line reads with each
owner only once (e.g., "flashinfer/cudnn/ @Anerudhan @yzh119 @bkryu @cyx-6"),
and commit the change; additionally, inspect and fix the automation script that
generates CODEOWNERS to prevent emitting duplicate usernames (dedupe the owner
list before writing).