Add to CODEOWNER

[aleozlx]

extra moe owner from internal team and diversify timezone coverage

📌 Description

🔍 Related Issues

🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull request, please make sure the following items are complete.

✅ Pre-commit Checks

• I have installed pre-commit by running pip install pre-commit (or used your preferred method).
• I have installed the hooks with pre-commit install.
• I have run the hooks manually with pre-commit run --all-files and fixed any reported issues.

If you are unsure about how to set up pre-commit, see the pre-commit documentation.

🧪 Tests

• Tests have been added or updated as needed.
• All tests are passing (unittest, etc.).

Reviewer Notes

Summary by CodeRabbit

• Chores
  • Updated internal code ownership configuration for maintenance paths.

---

Note: This release contains no user-facing changes. The update is purely internal infrastructure maintenance.

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the .github/CODEOWNERS file to integrate a new team member, @samuellees, into the review process for core components and specifically for the Mixture of Experts (MOE) related code. This strategic addition enhances review capacity and ensures broader timezone coverage for critical parts of the codebase.

Highlights

• CODEOWNERS Update: Added @samuellees as a CODEOWNER to the core maintainers section and the MOE-related directories (csrc/fused_moe/, flashinfer/fused_moe/, tests/moe/).
• Team Diversification: This change aims to expand the pool of MOE owners from the internal team, thereby diversifying timezone coverage for code reviews.

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

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 457409fc-e548-41d4-acb5-ef2f96c7de8d

📥 Commits

Reviewing files that changed from the base of the PR and between 1de1b97 and d17c5b6.

📒 Files selected for processing (1)

• .github/CODEOWNERS

---

📝 Walkthrough

Walkthrough

Updated .github/CODEOWNERS to add @samuellees to the core-maintainer catch-all reviewers list and designate them as a code owner for MOE-related paths including csrc/fused_moe/, flashinfer/fused_moe/, and tests/moe/.

Changes

Cohort / File(s)	Summary
Ownership Configuration .github/CODEOWNERS	Added @samuellees to catch-all core maintainers and assigned as code owner for MOE-related paths: csrc/fused_moe/, flashinfer/fused_moe/, and tests/moe/.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: Update CODEOWNERS #2218: Updates CODEOWNERS ownership for MOE-related paths including csrc/fused_moe/ and flashinfer/fused_moe/
• chore: Update CODEOWNERS #2152: Modifies CODEOWNERS entries for MOE-related paths in csrc/fused_moe and flashinfer/
• chore: Update CODEOWNERS #2719: Updates CODEOWNERS ownership mappings with overlapping path entries

Suggested labels

maintenance

Suggested reviewers

• kahyunnam
• yzh119

Poem

🐰 A rabbit hops through code so bright,
Adding keepers to MOE's might,
Samuel's now the guardian true,
Of fused_moe paths, old and new! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title "Add to CODEOWNER" is vague and generic, lacking specificity about which person is being added or for which code areas.	Use a more specific title like "Add @samuellees as CODEOWNER for MOE-related paths" to clearly identify the change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes a meaningful summary of the change ("extra moe owner from internal team and diversify timezone coverage") but the template sections are mostly unfilled with only placeholder comments.
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
• Commit unit tests in branch aleozlx-patch-owners-1

---

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

[claude]

Code Review

This is a straightforward CODEOWNERS update — adding @samuellees to both the catch-all reviewer list and all three MOE-specific paths. A few observations:

What looks good

• The change is minimal and focused: exactly 4 lines changed, all consistent.
• MOE paths are covered completely: csrc/fused_moe/, flashinfer/fused_moe/, and tests/moe/ all receive the new owner — no partial coverage.
• The new handle is appended consistently at the end of each entry, matching the existing style.

Minor suggestions

1. PR description is empty. The template fields (Description, Related Issues) are blank. It would help to briefly note who @samuellees is and why timezone diversification motivated this change (e.g., their timezone/location). This makes the git history more useful for future maintainers.

2. Catch-all vs. MOE-specific ownership: Adding @samuellees to the catch-all * rule means they'll be requested as a reviewer on every PR, not just MOE ones. If the intent is MOE-focused coverage, it may be worth keeping them only in the MOE section to avoid reviewer fatigue. That said, if they are indeed a core maintainer, the catch-all is appropriate — just worth a conscious decision.

3. No functional/test concerns — this file has no runtime impact, no security implications, and no performance considerations.

Overall this is a clean, low-risk change. The empty PR description is the only thing worth addressing before merge.

[gemini-code-assist]

Code Review

This pull request adds @samuellees as a code owner to the catch-all section and the MOE-related sections. The changes are straightforward, but the new entries (and existing ones) do not follow the alphabetical sorting convention mentioned in the CODEOWNERS file header. I've added suggestions to sort the owner lists for better maintainability.

[jimmyzho]

helping unblock