Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workspace: add CODEOWNERS #331

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

hinto-janai
Copy link
Contributor

@hinto-janai hinto-janai commented Oct 31, 2024

What

Adds a CODEOWNERS file to the repo, see here for more documentation: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.

Why

Code owners are automatically requested for review when someone opens a pull request that modifies code that they own. Code owners are not automatically requested to review draft pull requests.

@github-actions github-actions bot added the A-workspace Changes to a root workspace file or general repo file. label Oct 31, 2024
CODEOWNERS Outdated
Comment on lines 4 to 5
# Default owner(s) of all code.
* @Boog900 @hinto-janai
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ordering matters, @Boog900 will appear at the top in the reviewers list and so-on.

CODEOWNERS Outdated
Comment on lines 7 to 8
# hinto-janai
/benches/** @hinto-janai
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the last matching pattern takes the most precedence

In this case, changes to /benches will tag @hinto-janai first then everyone else (including everyone in *). I added myself for things I want to review.


Other notes:

  • Users listed here must have write access (I tried adding @dimalinux for cryptonight/ although it doesn't work)
  • @SyntheticBird45 I did not add you in * because every PR will tag you for review (and spam your email/notifications), did you want to be in this group or other paths/?

@Boog900 you need to enable the codeowner ruleset for main:

  1. Cuprate/cuprate Settings
  2. Code and automation
  3. Rulesets
  4. Require a pull request before merging
  5. Require review from Code Owners

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hinto-janai I'm already registered to any changes in the repository and receive mails accordingly. You can add me to it

@hinto-janai hinto-janai marked this pull request as ready for review December 3, 2024 01:13
@hinto-janai hinto-janai added the P-low Low priority. label Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-workspace Changes to a root workspace file or general repo file. P-low Low priority.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants