-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Consider rebuilding the UI based on CLI arguments/options. #38
Comments
A lot of those options grew organically, and its a little bit of a mess at this point. I agree that a cli with flag options would be cleaner, but in the spirit of inclusive-ness I'd like to keep the interactive option. Some defaults like username for calendar can be read from git global settings, etc. Another issue / usability concern is running gitfiti multiple times against the same repository blows away the generated script on each run 👎. |
Adding an option to specify a custom output filename or write to STDOUT would be the obvious fix. If none is given, the ouput filename could be extended with a (preferrably human-readable) timestamp. |
While the current interactive UI seems nice at first, it becomes tiresome when used frequently.
Giving a single wrong value or trying another image requires walking through the whole process again.
Using a command-line interface instead would allow users to re-use and slightly adjust the command they just issued on the shell, and to create very basic shell scripts as some form of configuration file/wrapper.
<Enter>
on every run.etc., you get the idea.
Then again, CLI arguments could be implemented, but gitfiti could still provide an interactive frontend for newcomers, leaving the former to more experienced, power-hungry users.
The text was updated successfully, but these errors were encountered: