-
Notifications
You must be signed in to change notification settings - Fork 9
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
Improve user experience when using this tool as a CLI #36
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
/priority backlog |
/sig user-experience |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Is your feature request related to a problem? Please describe.
When I tried thoth-glyph, it produced the following output for me:
Sadly, I see just first 5 commits and last 5 commits classified. It would be nice to produce the whole classification to standard output and let the user (if required) filter messages.
Other suggestions:
the output could have the commit sha of the commit being classified
the output could be in an easily processable form by tools (e.g. coreutils) by default
merge commits could be removed from the output
formatter could be selected as a CLI option to have a tool that can be easily used on the command line, e.g.:
use dashes instead of underscores in the command-line options
improve help messages (e.g.
classify
sub-command says the classification is done for the current git repo, but it is done for the commit message passed as argument)The text was updated successfully, but these errors were encountered: