-
Notifications
You must be signed in to change notification settings - Fork 24
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
Is there a way to automate the prompts? #115
Comments
its a inconsistency that i wanna fix across the commands soon(ish)... it would probably looks like the flags on
|
@DanielTate in the new release i add the flags to manual and in commands, could you take a look and tell me if it helps you? |
@lucassabreu Thanks for looking at this. I tried the commands you listed and without option flags found here: And still couldn't get it to work. I tried
Both just gave me the next prompt to select a project. I tried the --allow-incomplete flag on both with no luck. Up updated my package using |
it will ask you to confirm da arguments id you have "interactive mode" turned on. you can turn it off using I think I didn't understand the issue now hehe, of what you wanted is the not to ask for confirmation, than use that flag. you can disable it using the environment variable |
Thanks that works! Since I'm using the snap I don't think I can use the config file? It says in your Read me. It would be very helpful to provide this |
@DanielTate i changed the help of
what do you think? releated to #117 |
That seems helpful. If you have an example of a non interactive input in your Readme I think that would be very helpful also. I am the kind of person that looks at examples before reading the manual. I think many people are like this. |
i added a example using only flags to README.md ;) |
For example if I use
clockify-cli manal
I have to follow prompts to put in a record is there a way to instead:
If not are there any plans to implement this kind of API?
clockify-cli manual -idPROJECT_ID -dDESCRIPTION -tTAG,TAG -s09:00 -e17:00
The text was updated successfully, but these errors were encountered: