codeowners-checker
codeowners-checker copied to clipboard
Check .github/CODEOWNERS consistency
Stale???
Is this project no longer being supported? Dependencies are outdated and becoming a problem for utilization.
Hi Folks, I want to share some thoughts that I've been having while playing around with this gem and implementing the cleanup command. The reason for opening an issue here...
## Motivation At the moment all files that do not have an owner are always taking into consideration for the final result. We also introduced a whitelist concept to ignore...
Adds a simple `list` command to verify ownership of files for a given owner. I found this useful when making changes to CODEOWNERS in large code bases with complex rules....
After some discussion I am suggesting to add a cleanup command to tackle the following problems: ## Problem When a CODEOWNERS file becomes bigger the following problems arise: * Duplicate...
I'm using a GitHub app to make API requests, which gives allows me to set finer permissions than through a personal access token. As I was looking through the code...
for `Config` class to work correctly we had to patch the Git tickets are: - https://github.com/ruby-git/ruby-git/pull/398 - https://github.com/ruby-git/ruby-git/pull/399 - https://github.com/ruby-git/ruby-git/pull/400 after those tickets get merged we can cleanup our patches
I suggest adding a command to automatically add changed files (that don't match any existing rule) to the given owner. This would allow a contributor to assign all the changes...
# Rationale Right now descendant's of `Line` use `parse` in `initialize` (mostly `Pattern`) and the `initialize` method always takes a raw line as param. Because of this we can not...