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
  • Internal code ownership and maintenance structure updates.

Note: This release contains no user-facing changes. Updates are limited to internal development governance and team organization.

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

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Updated .github/CODEOWNERS with reorganized ownership mappings: reordered, added, and removed owners across many top-level paths and subpaths (benchmarks/, csrc/ and its subdirectories, flashinfer/ and its subpaths including new flashinfer/triton/kernels/, include/, docs/, and scripts/). No code behavior changes.

Changes

Cohort / File(s)	Summary
CODEOWNERS (single file) .github/CODEOWNERS	Major reorganization of ownership entries: reordered owner lists, added/removed owners, introduced new public paths (e.g., flashinfer/triton/kernels/, include/flashinfer/), and updated ownership across benchmarks/, csrc/ (many subpaths), flashinfer/ (many subpaths), include/, docs/, and scripts/. No code changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify owner lists and ordering for sensitive areas: csrc/ subpaths, flashinfer/ subpaths, and include/flashinfer/.
• Confirm new path flashinfer/triton/kernels/ uses intended owners and formatting.
• Check for duplicate/contradictory entries or path overlaps that affect matching precedence.

Possibly related PRs

• chore: Update CODEOWNERS #2152 — Overlapping edits to .github/CODEOWNERS (reordering and owner changes across csrc, flashinfer, include, scripts).
• chore: Update CODEOWNERS #2098 — Similar CODEOWNERS updates touching benchmarks, csrc, flashinfer, and include ownership mappings.
• chore: Update CODEOWNERS #1949 — Overlapping ownership reassignments in .github/CODEOWNERS for csrc, flashinfer, include, docs, and scripts.

Suggested reviewers

• yzh119
• nvmbreughe
• bkryu

Poem

🐰
I hopped through lines of owners new,
I nudged the paths so names fit true,
Triton kernels now have a home,
Old order shuffled — fields to roam,
A tiny hop, a tidy crew. 🥕

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 describes the main change—updating the CODEOWNERS configuration file based on commit history analysis.
Description check	✅ Passed	The PR description includes a clear summary, specific details about changes, review instructions, and contextual notes about the automated process; however, it does not follow the provided repository template structure.
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

---

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 ensures the project's code ownership definitions remain accurate and up-to-date by automatically revising the .github/CODEOWNERS file. This process leverages recent commit history to identify the most relevant contributors for various modules, thereby streamlining the code review process and ensuring that review assignments are routed to the appropriate experts.

Highlights

• Automated CODEOWNERS Update: This pull request automatically updates the .github/CODEOWNERS file to reflect current code ownership.
• Ownership Recalculation Logic: Code ownership is recalculated based on commit frequency, file coverage, and commit recency over the last 180 days, with a minimum commit threshold of 1.
• New Path Ownership: A new path, flashinfer/triton/kernels/, has been added to the CODEOWNERS file, assigning @yzh119 as its owner.

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 automatically updates the CODEOWNERS file based on recent git history. The changes mostly involve reordering owners based on contribution activity and adding a new entry. I've found one issue where a user is listed as an owner twice for the flashinfer/cudnn/ path. This is likely due to a bug in the generation script and should be corrected. Otherwise, the changes look reasonable.

[gemini-code-assist]

The user @Anerudhan is listed twice as an owner for this path. This is redundant and should be corrected. While GitHub may handle this gracefully, it's best to keep the CODEOWNERS file clean and free of duplicates.

This might indicate a bug in the automation script that generates this file, which should probably be investigated to prevent this from happening in the future.

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

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

.github/CODEOWNERS (1)

28-28: Remove duplicate owner from the list.

The user @Anerudhan appears twice in the owner list for flashinfer/cudnn/. This redundancy should be corrected. Additionally, the automation script that generates this file should be enhanced to detect and remove duplicates automatically.

Apply this diff to fix:

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

🧹 Nitpick comments (1)

.github/CODEOWNERS (1)

12-13: Consider adding backup owners for bus factor resilience.

Lines 12, 13, and 39 each have only a single owner. While this accurately reflects current commit patterns, consider identifying backup maintainers for these paths to reduce bus factor risk, especially for critical infrastructure.

Also applies to: 39-39

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6803665 and c60a9ef.

📒 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