Replies: 5 comments
-
i would go with teams, which seems easier to manage. dont need to have PR with changes if you want to add somebody.
just from top of my head |
Beta Was this translation helpful? Give feedback.
-
@michalpristas would those be represented by wildcards in the codeowners file? Also, would we create Github teams for each of those categories? |
Beta Was this translation helpful? Give feedback.
-
I think we have to create teams in GitHub to assign them to portions of the codebase. I don't believe you can assign more than one person or entity as an owner, one |
Beta Was this translation helpful? Give feedback.
-
@arschlesI meant in a way how @robjloranger described |
Beta Was this translation helpful? Give feedback.
-
I like the initial ideas @michalpristas had here #806 (comment) We can always adjust as we move along. I'm happy to create the teams today if that's somewhere we'd like to start. |
Beta Was this translation helpful? Give feedback.
-
The current CODEOWNERS file has only one line - everything is "owned" by @gomods/maintainers. We have a bigger community now, and a super different codebase, than we did when we committed that file.
Should we add more lines to the file so that we have different directories specialized to particular people/teams?
Beta Was this translation helpful? Give feedback.
All reactions