Package Exports
- github-codeowners
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (github-codeowners) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
github-codeowners
A CLI tool for working with GitHub CODEOWNERS.
Things it does:
- Output who owns each file in your repo (ignoring files listed in
.gitignore) - Output who owns a single file
- Output ownership information at a specific git commit
- Output ownership information of staged files
- Outputs lots of lovely stats
- Outputs handy formats for integrations (CSV and JSONL)
Installation
Install via npm globally then run
$ npm i -g github-codeowners
$ github-codeowners --help
Usage: github-codeowners [options] [command]Commands
Audit
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)
Loved: 10 files (494 lines)
Unloved: 14 files (884 lines)
--- Owners ---
@jjmschofield: 10 files (494 lines)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
.gitignoreOutput 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,@jjmschofieldFull 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: "/Users/jjmschofield/projects/github/github-codeowners")
-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)
-s, --stats output stats (default: true)
-i, --include <partialPath> paths begening with partial path only (default: '')
-h, --help output usage informationWho
Tells you who owns a given file:
$ cd <your awesome project>
$ github-codeowners who <file>
<file> @some/teamFull usage:
$ github-codeowners who --help
Usage: github-codeowners who [options] <file>
lists owners of a specific file
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 informationGit
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 gitOwnership 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 -sFull 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 informationOutput Formats
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 choice
Limits and Things to Improve
- It requires node
- It is not optimized
- The output interface might change
- Command syntax might change
Shout outs
Inspired by codeowners but implemented in Typescript with extra bells and whistles.