-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal: rename executable to masonry
#177
Labels
Comments
masonry
masonry
Or just rename the entire project to 'masonry'? |
redhatrises
added a commit
to redhatrises/compliance-masonry
that referenced
this issue
Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses - New masonry.go is now the primary program naming - Fixes opencontrol#177
redhatrises
added a commit
to redhatrises/compliance-masonry
that referenced
this issue
Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses - New masonry.go is now the primary program naming - Fixes opencontrol#177
redhatrises
added a commit
to redhatrises/compliance-masonry
that referenced
this issue
Jun 8, 2018
- Create a new compliance-masonry executable for legacy uses - New masonry.go is now the primary program naming - Fixes opencontrol#177
@afeld @pburkholder the CLI was renamed through #291. Should we also rename the repo? GitHub automatically takes care of redirects, so docs/presentations/etc would automatically get forwarded. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't think that name is taken by any major tool, and it's faster to type than
compliance-masonry
. If, however, it makes lots of tools that assume an executable of the package name harder to use, it's not worth it.The text was updated successfully, but these errors were encountered: