Skip to content

Conversation

@jbampton
Copy link
Member

People with write permissions for the repository can create or edit the CODEOWNERS file and be listed as code owners.

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

See the link below for an example of how a CODEOWNERS file works:

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file

Did you read the Contributor Guide?

Is this PR related to a ticket?

  • No this is a CI update. The PR name follows the format [CI] my subject

What changes were proposed in this PR?

I am a committer with write access and I work on the pre-commit config all the time so I should be one of the default people that get called for a review when others work on our pre-commit framework.

How was this patch tested?

When you visit the CODEOWNERS file on the GitHub website it will tell you if it is valid or not.

For example go here:

https://github.com/apache/sedona/blob/master/.github/CODEOWNERS

And you will see this:

Screenshot from 2025-03-29 14-37-10

Did this PR include necessary documentation updates?

  • No, this PR does not affect any public API so no need to change the documentation.

@jbampton jbampton self-assigned this Mar 29, 2025
@jbampton jbampton requested a review from jiayuasu as a code owner March 29, 2025 04:41
@jiayuasu jiayuasu merged commit 141a368 into apache:master Mar 29, 2025
4 checks passed
@jbampton jbampton deleted the update-codeowners-file branch March 29, 2025 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants