Skip to content

Support executable_name in config and API - #86

Merged
perryqh merged 7 commits into
mainfrom
ph.executable-name
Dec 17, 2025
Merged

Support executable_name in config and API#86
perryqh merged 7 commits into
mainfrom
ph.executable-name

Conversation

@perryqh

@perryqhperryqh commented Dec 3, 2025

Copy link
Copy Markdown
Contributor

What problem is this solving?

The current error message — CODEOWNERS out of date. Run 'codeowners generate' to update the CODEOWNERS file — assumes the executable is named codeowners. However, this isn’t always true, such as when using codeowners-rs via the code_ownership
gem.

To prevent confusion for end users, this change introduces a new executable_name configuration option. It allows projects to specify the actual executable name so the error message accurately reflects the correct command to run.

Other:

  • Bumped the crate version from 0.3.0 to 0.3.1 to reflect the new feature.

@corsonknowlescorsonknowles left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To my admittedly Ruby-centric eyes, this looks well tested and like it does the thing.

Thanks for designing and shipping the solution here!

Should the PR description be more explicit that this is meant to support wrappers/executables in CI/repos? Add docs?

@perryqhperryqh changed the title Support executable_name in configSupport executable_name in config and APIDec 4, 2025
@perryqh
perryqh merged commit 68a5e19 into mainDec 17, 2025
8 checks passed
@github-project-automationgithub-project-automationBot moved this from Triage to Done in ModularityDec 17, 2025
@dduuggdduugg mentioned this pull request Apr 16, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants

@perryqh@martinemde@corsonknowles