Describe your repository ownership with teams.json. Configure your teams, contexts, and let teams.json generate common configuration files for you.
Every teams.json has a "teams"
property that describes the teams in your repository. Teams own things. Our opinion
is that teams own contexts, folders, or files.
Tests can be executed with npm test
. There are test and fixtures in ./tests
directory.
Run a build with npm run build
.
Running teams can be done with npm run teams
.
teams.json ships with some plugins ready to go. You can list all detected plugins with plugins:list
.
-
codeowners
plugin will generate your CODEOWNERS file for you.
- Allow more flexible exensibility of other outputs. Idea would be that
"plugins"
directive in teams.json can point to any other plugin file and be run. (E.g. datadog output, or argo workflow generators) - Bring "urls" back into the mix
- Linting. Audit a folder to detect "unowned" things.
- Linting. Audit team.json itself for unowned contexts.