Repository navigation
chore: codeowners - #666
Conversation
…d primary devs also
There was a problem hiding this comment.
I've suggested some changes.
In addition, perhaps we would want to add a workflow that makes sure all high level folders are represented in this file? So we avoid creating a new folder and not knowing who the owner is.
EDIT:
PR #666 - stay away!
| /medcat/ @mart-r @adam-sutton-1992 @vladd-bit | ||
| /medcat-den/ @CogStack/cogstack-development @mart-r | ||
| /medcat-model-distributor/ @CogStack/cogstack-development @mart-r | ||
| /medcat-plugins/ @CogStack/cogstack-development @mart-r |
There was a problem hiding this comment.
There's a fair few plugins in there, some of which (i.e transformers NER and embedding linker) were created by Adam, so I'd add him here as welll.
| /.devcontainer/ @CogStack/cogstack-development | ||
| /.github/ @mart-r @tomolopolis @vladd-bit @adam-sutton-1992 | ||
| /anoncat-demo-app/ @CogStack/cogstack-development | ||
| /cogstack-es/ @CogStack/cogstack-development |
There was a problem hiding this comment.
Can put me in here.
But I don't fully know if anyone is using this. So may need to investigate whether we want to keep it.
I think it is certainly a nice way to unify the way people interact with everything but only if / when people use it. The other issue is that this exposes only a small subset of functionality that ES or OS have.
| @@ -0,0 +1,26 @@ | |||
| # Code owners for each top-level directory. | |||
| # | |||
| # Default owner is @CogStack/cogstack-development. A directory lists individual | |||
There was a problem hiding this comment.
Do we need this overview?
Reads like the AI agent telling you what they've done rather than an instruction for someone else editing this in the future.
mart-r
left a comment
mart-r
left a comment
There was a problem hiding this comment.
Let's roll this out and make changes if/when needed.
Uh oh!
There was an error while loading. Please reload this page.