design-reviewers and engineer-reviewers as codeowners #2621
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
This comment was marked as resolved.
This comment was marked as resolved.
|
@jonrohan Curious validation errors on codeowners 馃
|
jonrohan
approved these changes
May 6, 2024
There was a problem hiding this comment.
@siddharthkp should be good now, the teams needed to have primer/css added to the repositories list
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.
What are you trying to accomplish?
In codeowners, swap css-reviewers with design-reviewers + engineer-reviewers
What approach did you choose and why?
For now, I have only added engineering-reviews on package files so that they can share the load of dependabot PRs (especially during first responder)
Can these changes ship as is?