feat: Add CODEOWNERS file and configure branch protection to restrict…

[NotYuSheng]

… access to dev branch

[gemini-code-assist]

Summary of Changes

Hello @NotYuSheng, 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 enhances repository governance and security by establishing clear code ownership and implementing stricter access controls for the dev branch. The changes aim to ensure that critical branches are well-protected and that code changes are reviewed by designated owners.

Highlights

• Code Ownership: Introduced a new .github/CODEOWNERS file to define code ownership for the repository. This file designates @NotYuSheng as the owner for all files.
• Branch Protection: Configured branch protection rules, specifically for the dev branch, to restrict access. This is a key step in enhancing the security and integrity of the dev branch.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 introduces a .github/CODEOWNERS file, setting @NotYuSheng as the default owner for all files. This is a key step for enabling branch protection rules that require reviews from code owners, as suggested by the PR title. My primary feedback focuses on verifying the specified username and ensuring the user has the necessary write permissions for the CODEOWNERS functionality to operate correctly and effectively enforce branch restrictions. I've also included a suggestion for considering more granular ownership as the project scales.