Package Exports
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 (codeowners-git) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
codeowners-git
Managing large-scale migrations in big monorepos with multiple codeowners can be overwhelming. Massive PRs touching thousands of files make it hard for teams to review changes efficiently.
codeowners-git solves this by:
- Identifying files owned by specific teams using the CODEOWNERS file.
- Creating compact, team-specific branches with only their affected files.
- Streamlining the review process with smaller, targeted PRs.
Installation
Using npx (recommended)
Run commands directly without installation:
npx codeowners-git <command>Install globally via npm
npm install -g codeowners-gitThen run commands directly:
codeowners-git <command>Configuration
The tool automatically detects CODEOWNERS files in:
.github/CODEOWNERSdocs/CODEOWNERSCODEOWNERS(root directory)
Commands
list
List current CODEOWNERS entries.
Usage:
codeowners-git list [options]Options:
--owner, -oFilter by specific owner--include, -iInclude specific patterns
Example:
codeowners-git list -o @myteambranch
Manage branch permissions in CODEOWNERS file.
Usage:
codeowners-git branch [options]Options:
--owner, -oSpecify owner(s) to add/remove--branch, -bSpecify branch pattern--message, -mCommit message for changes
Example:
codeowners-git branch -o @myteam -b "feature/*" -m "Add feature branch ownership"Contributing
- Clone the repository
- Install dependencies:
bun install- Make your changes
- Run tests:
bun test- Submit a pull request
License
MIT ©