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

Use the kpt-reviewers team for single-assignment #3619

Merged
merged 1 commit into from
Oct 14, 2022

Conversation

justinsb
Copy link
Contributor

@justinsb justinsb commented Oct 14, 2022

Avoid assigning to everyone (as then nobody feels responsible); assign to one person from the kpt-reviewers team.

Avoid assigning to everyone (as then nobody feels responsible); assign
to one person from the kpt-reviewers team.

# Docs
/site @bgrant0607 @droot @justinsb @mortent @natasha41575 @yuwenma
/site @GoogleContainerTools/kpt-reviewers
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to specify separate owners for all these paths, when we use the same group for all of them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, I would guess not. Let me try this PR and then I can clean up if the single-assignment works as expected :-)

@justinsb justinsb merged commit 37f513e into kptdev:main Oct 14, 2022
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.

2 participants