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

docs: update CODEOWNERS file to use the eng-general-maintainers team #30

Merged
merged 1 commit into from
May 29, 2024

Conversation

jtieri
Copy link
Contributor

@jtieri jtieri commented May 29, 2024

Update CODEOWNERS to use the engineering general maintainers team so that way the entire org is not getting alerts for activity in the OSS template repo.

At the same time I have adjusted the settings on the eng-general-maintainers team so that for each PR a random member of the team will be selected for code review. When a member from the team is selected it will only send notifications to the selected team member instead of the entire team. We will make use of the load balance algorithm which attempts to balance the load across the entire team by taking in account the current number of PRs assigned to each member of the team. see: https://docs.github.com/en/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team#routing-algorithms

Closes #27

Update CODEOWNERS to use the engineering general maintainers team so that way the entire org is not getting alerts for activity in the OSS template repo.
@jtieri jtieri enabled auto-merge (squash) May 29, 2024 20:00
Copy link
Member

@joelsmith-2019 joelsmith-2019 left a comment

Choose a reason for hiding this comment

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

Looks good to me! Would it make sense to select 2 people to review the PR?

@jtieri jtieri merged commit 8615b58 into main May 29, 2024
9 of 10 checks passed
@jtieri jtieri deleted the justin/update-codeowners branch May 29, 2024 20:06
@jtieri
Copy link
Contributor Author

jtieri commented May 29, 2024

Looks good to me! Would it make sense to select 2 people to review the PR?

That is a great question. Picking two members of the team for code review but only requiring approval from one could be a good way to ensure that PRs are being reviewed quickly. In the past we have only ever had it select one reviewer but I'm not opposed to this.

@beckettsean do you have any thoughts on this?

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.

[Bug]: PRs should default to an engineering team for review, not all-write
2 participants