gagoar/codeowners-generator
CODEOWNERS generator for mono-repos. This action will run codeowners-generator on your project and apply changes
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| use-maintainers | For every package.json found, generate a CODEOWNERS entry using the maintainers field | no | false |
| group-source-comments | Instead of generating one comment per rule, enabling this flag will group them, reducing comments to one per source file. Useful if your codeowners file gets too noisy | no | false |
| custom-regeneration-command | Specify a custom regeneration command to be printed in the generated CODEOWNERS file, it should be mapped to run codeowners-generator | no | false |
| check | It will fail if the CODEOWNERS generated does not match the current (or missing) CODEOWNERS. Useful for validating that the CODEOWNERS file is up to date during CI.' | no | false |
| output | The output path and name of the file, (default: CODEOWNERS) | no | CODEOWNERS |
| preserve-block-position | Keep the generated block in the same position it was found in the CODEOWNERS file (if present). Useful for when you make manual additions. | no | false |
| includes | The glob used to find CODEOWNERS files in the repo. Defaults to the value in src/utils/constants.ts | no | "" |
| version | codeowners-generator version. It will default to the latest in npm otherwise' | no | — |
| hidden-directories | Also include searching in hidden (dot) directories. | no | false |
Outputs
no outputs