
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@snyk/github-codeowners
Advanced tools
Handy tool for working with file ownership using Githubs CODEOWNERS file
A CLI tool for working with GitHub CODEOWNERS.
Things it does:
.gitignore
)Install via npm globally then run
$ npm i -g github-codeowners
$ github-codeowners --help
Usage: github-codeowners [options] [command]
Compares every file in your current (or specified) directory against your CODEOWNERS rules and outputs the result of who owns each file.
$ cd <your awesome project>
$ github-codeowners audit
README.md
package.json
src/cli.ts @jjmschofield
...
Ownership stats:
$ github-codeowners audit -s
--- Counts ---
Total: 24 files (1378 lines) 100%
Loved: 10 files (494 lines) 41.6%
Unloved: 14 files (884 lines) 58.4%
--- Owners ---
@jjmschofield: 10 files (494 lines) 41.6%
Only files in a specific directory:
$ github-codeowners audit -r src/
src/cli.ts @jjmschofield
src/commands/audit.ts @jjmschofield
...
Only unowned files:
$ github-codeowners audit -u
.github/CODEOWNERS
.gitignore
Output in JSONL:
$ github-codeowners audit -o jsonl
{"path":"src/commands/audit.ts","owners":["@jjmschofield"],"lines":48}
...
Output in CSV:
$ github-codeowners audit -o csv
src/commands/audit.ts,@jjmschofield
Full usage information:
$ github-codeowners audit --help
Usage: github-codeowners audit [options]
list the owners for all files
Options:
-d, --dir <dirPath> path to VCS directory (default: "<current working directory>")
-c, --codeowners <filePath> path to codeowners file (default: "<dir>/.github/CODEOWNERS")
-o, --output <outputFormat> how to output format eg: simple, jsonl, csv (default: "simple")
-u, --unloved unowned files only (default: false)
-g, --only-git consider only files tracked by git (default: false)
-s, --stats output stats (default: true)
-r, --root <rootPath> the root path to filter files by (default: "")
-h, --help output usage information
Tells you who owns a given file or files:
$ cd <your awesome project>
$ github-codeowners who <file> <file>
<file> @some/team
<file> @some/team
Full usage:
$ github-codeowners who --help
Usage: github-codeowners who [options] <file...>
lists owners of a specific file or files
Options:
-d, --dir <dirPath> path to VCS directory (default: "/Users/jjmschofield/projects/github/snyk/registry")
-c, --codeowners <filePath> path to codeowners file (default: "<dir>/.github/CODEOWNERS")
-o, --output <outputFormat> how to output format eg: simple, jsonl, csv (default: "simple")
-h, --help output usage information
Provides a list of files with their owners between commits (against the current version of CODEOWNERS).
Ownership of all files staged for commit:
$ cd <your awesome project>
$ github-codeowners git
Ownership of files existing at a specific commit:
$ github-codeowners git <commit sha>
Ownership of files changed between two commits:
$ github-codeowners git <commit sha> <commit sha>
Output stats:
$ github-codeowners git -s
Full usage:
$ github-codeowners git --help
Usage: github-codeowners git [options] [shaA] [shaB]
lists owners of files changed between commits, a commit against head or staged against head.
Options:
-d, --dir <dirPath> path to VCS directory (default: "/Users/jjmschofield/projects/github/snyk/registry")
-c, --codeowners <filePath> path to codeowners file (default: "<dir>/.github/CODEOWNERS")
-o, --output <outputFormat> how to output format eg: simple, jsonl, csv (default: "simple")
-s, --stats output stats, note line counts are not available for this command (default: false)
-h, --help output usage information
Validates your CODEOWNERS file to find common mistakes, will throw on errors (such as malformed owners).
$ cd <your awesome project>
$ github-codeowners validate
Found duplicate rules [ 'some/duplicate/rule @octocat' ]
Found rules which did not match any files [ 'some/non-existent/path @octocat' ]
...
Full usage information:
$ github-codeowners validate --help
Usage: github-codeowners validate [options]
Validates a CODOWNER file and files in dir
Options:
-d, --dir <dirPath> path to VCS directory (default: "<current working directory>")
-c, --codeowners <filePath> path to codeowners file (default: "<dir>/.github/CODEOWNERS")
-r, --root <rootPath> the root path to filter files by (default: "")
-h, --help output usage information
Check github-codeowners <command> --help
for support for a given command, however generally the following outputs are supported:
simple
- tab delimited - terminal friendly outputjsonl
- line separated json - useful for streaming data to another commandcsv
- csv delimited fields - useful to import into a spreadsheet tool of your choiceInspired by codeowners but implemented in Typescript with extra bells and whistles.
This project is a fork of jjmschofield's version.
FAQs
Handy tool for working with file ownership using Githubs CODEOWNERS file
We found that @snyk/github-codeowners 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 for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.