Reduce team review request noise from CODEOWNERS #687
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `CODEOWNERS` file has been adjusted to request review from the primary repository maintainer for files that are typically updated via automation, rather than requesting review from the whole team. This: - reduces team notification/review request noise for Dependabot and release automation PRs, given that other members on the team usually aren't going to look at such PRs anyway, and it only makes it harder for team members to see the review requests that are actually in their queue - retains the "team awareness" benefit of having the team see notifications for all other non-automated PRs - retains the UX benefit of having a reviewer be automatically selected In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled). For supported syntax, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners GUS-W-14941625.
Add requirements.txt to explicit CODEOWNERS mappings
dzuelke
approved these changes
Feb 2, 2024
Merged
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
The `CODEOWNERS` file has been adjusted to request review from the primary repository maintainer for files that are typically updated via automation, rather than requesting review from the whole team. This: - reduces team notification/review request noise for Dependabot and release automation PRs, given that other members on the team usually aren't going to look at such PRs anyway, and it only makes it harder for team members to see the review requests that are actually in their queue - retains the "team awareness" benefit of having the team see notifications for all other non-automated PRs - retains the UX benefit of having a reviewer be automatically selected In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled). For supported syntax, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners GUS-W-14941625.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
The `CODEOWNERS` file has been adjusted to request review from the primary repository maintainer for files that are typically updated via automation, rather than requesting review from the whole team. This: - reduces team notification/review request noise for Dependabot and release automation PRs, given that other members on the team usually aren't going to look at such PRs anyway, and it only makes it harder for team members to see the review requests that are actually in their queue - retains the "team awareness" benefit of having the team see notifications for all other non-automated PRs - retains the UX benefit of having a reviewer be automatically selected In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled). For supported syntax, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners GUS-W-14941625.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
The `CODEOWNERS` file has been adjusted to request review from the primary repository maintainer for files that are typically updated via automation, rather than requesting review from the whole team. This: - reduces team notification/review request noise for Dependabot and release automation PRs, given that other members on the team usually aren't going to look at such PRs anyway, and it only makes it harder for team members to see the review requests that are actually in their queue - retains the "team awareness" benefit of having the team see notifications for all other non-automated PRs - retains the UX benefit of having a reviewer be automatically selected In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled). For supported syntax, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners GUS-W-14941625.
robinwo
pushed a commit
to robinwo/heroku-buildpack-php
that referenced
this pull request
Sep 13, 2024
The `CODEOWNERS` file has been adjusted to request review from the primary repository maintainer for files that are typically updated via automation, rather than requesting review from the whole team. This: - reduces team notification/review request noise for Dependabot and release automation PRs, given that other members on the team usually aren't going to look at such PRs anyway, and it only makes it harder for team members to see the review requests that are actually in their queue - retains the "team awareness" benefit of having the team see notifications for all other non-automated PRs - retains the UX benefit of having a reviewer be automatically selected In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled). For supported syntax, see: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners GUS-W-14941625.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
CODEOWNERSfile has been adjusted to request review from the primary repository maintainer for files that aretypically updated via automation, rather than requesting review from the whole team.
This:
In the scenarios where either the primary repository maintainer is away, or they are the person opening the PR (so can't request review from themselves), other team members will still be able to approve the PR with the changes I've made to the branch protection settings (unchecking "Require Code Owner Review", leaving "require approvals" enabled which can only be from teams with write access, which is only us. Plus for bonus points, the option to only permit merging from members of our team has also been enabled).
For supported syntax, see:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
GUS-W-14941625.