codeowners-enforcer
Advanced tools
Weekly downloads
Readme
Enforce
CODEOWNERS
files on your repo
With npm:
npm install --global codeowners-enforcer
With Cargo:
cargo install codeowners-enforcer
codeowners-enforcer
works by finding your CODEOWNERS
file in a known
location as defined by GitHub.
Then it walks through your file tree asserting that every file has a code owner.
If any files don't have a code owner, it will return their relative paths and
exit with 1
:
codeowners-enforcer
Oops! Found files without CODEOWNERS!
file.one
path/to/file.two
path/to/file.three
Fix: Please delete these files, move them, or add owners to them in /path/to/CODEOWNERS
If you want to return just the file paths, pass --quiet
or -q
:
codeowners-enforcer --quiet
one.txt
path/to/two.sh
path/to/three.py
If you want to ignore files, pass --ignore <pattern>
or -i
:
codeowners-enforcer --ignore "path/**/*.py"
one.txt
path/to/two.sh
You can also pass multiple ignores:
codeowners-enforcer -i "path/**/*.py" -i "path/**/*.sh"
one.txt
If you want to only check certain files, pass <patterns...>
:
codeowners-enforcer "**/*.sh" "**/*.py"
path/to/two.sh
path/to/three.py
FAQs
Enforce CODEOWNERS files on your repo
The npm package codeowners-enforcer receives a total of 754 weekly downloads. As such, codeowners-enforcer popularity was classified as not popular.
We found that codeowners-enforcer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.