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

WIP: Add CODEOWNERS #4551

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

WIP: Add CODEOWNERS #4551

wants to merge 4 commits into from

Conversation

pierremtb
Copy link
Collaborator

@pierremtb pierremtb commented Nov 22, 2024

Following an outside approval on #4516, it seems like this is something we should start having?

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

The team @KittyCAD/eng already has write access, and seems like a straightforward owner here. Could restrict to frontend at some point but I don't think it's needed now.

This coupled with this setting below turned on in the branch protection section should ensure only KittyCAD engineers approvals count toward the PR merge criterion.
image

Copy link

qa-wolf bot commented Nov 22, 2024

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

Copy link

vercel bot commented Nov 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
modeling-app ✅ Ready (Inspect) Visit Preview Dec 2, 2024 3:43pm

@jtran
Copy link
Collaborator

jtran commented Nov 22, 2024

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

With this change, we're all going to get requested as a reviewer on every PR. Is that intended?

I don’t personally like this change because the approval requirement isn’t meant to block merges. It’s meant to help spread knowledge and get more eyes on code. If someone makes a PR and someone on the outside approves, could people simply not merge?

@pierremtb
Copy link
Collaborator Author

@jtran Good point, the noise part would for sure be annoying. Would work better with a @kittycad/frontend team. Closing for now.

@pierremtb pierremtb closed this Nov 22, 2024
@pierremtb pierremtb reopened this Dec 2, 2024
@pierremtb
Copy link
Collaborator Author

Created @KittyCAD/frontend as a nested team under @KittyCAD/eng. So probably worth reopening this discussion? (low priority of course)

@jessfraz
Copy link
Contributor

jessfraz commented Dec 2, 2024

@pierremtb the bot will delete that group unless you add it here https://github.com/KittyCAD/configs/blob/main/configs/groups.toml

copying the settings for consultants should be fine, that way its internal only

@pierremtb
Copy link
Collaborator Author

@jessfraz ah thanks for the heads up, will PR there

@franknoirot
Copy link
Collaborator

I'm seeing an error message when I look at the code change:

Screenshot 2024-12-09 at 12 32 17 PM

@pierremtb
Copy link
Collaborator Author

Yeah me too @franknoirot. I did create https://github.com/KittyCAD/configs/pull/132 to at least populate that team and then we can come back here and see if we need anything else?

@pierremtb pierremtb changed the title Add CODEOWNERS WIP: Add CODEOWNERS Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants