Skip to content

Add @Adyen/api-library-maintainers to CODEOWNERS #827

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 6, 2025
Merged

Add @Adyen/api-library-maintainers to CODEOWNERS #827

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
* @Adyen/developer-relations
* @Adyen/developer-relations @Adyen/api-library-maintainers
Copy link

Choose a reason for hiding this comment

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

medium

Adding @Adyen/api-library-maintainers as a global owner will result in this team being requested for review on every pull request in the repository. The team's name suggests they have a specific focus on an API library. If that's the case, assigning global ownership might lead to notification fatigue from irrelevant review requests (e.g., for documentation or configuration changes).

Consider defining more granular ownership rules to target only the relevant parts of the codebase. This ensures that teams are only notified for changes within their scope of responsibility.

For example:

* @Adyen/developer-relations
/path/to/api/library/ @Adyen/api-library-maintainers

Please consider if this more specific approach would be a better fit for your repository's structure.