-
Notifications
You must be signed in to change notification settings - Fork 95
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
Move CLI to click #631
Comments
No, just dev effort and agree. I think there might already be an open issue? |
Got it, couldn't find it, I only found mentions of click in the issues. On (Apr-23-15|17:36), Daniel McDonald wrote:
|
ah, well you take the 🍰 :) |
If we move the CLI to click means that is a major release? Just checking cause it think I won't be backwards compatible, or am I missing something? |
yes On Thu, Apr 23, 2015 at 8:44 PM, josenavas notifications@github.com wrote:
|
3.0, here we go! On (Apr-23-15|19:49), Daniel McDonald wrote:
|
we could do a minor release i suppose On Thu, Apr 23, 2015 at 8:51 PM, Yoshiki Vázquez Baeza <
|
Just remember that backward compatibility is needed for |
Ya, so I was thinking 2.2 instead of 3.0 On Thu, Apr 23, 2015 at 9:15 PM, Greg Caporaso notifications@github.com
|
Ok, perfect. |
|
I've tested all of the commands presented on the website, and they're working as they did in 2.1.4. Closing this. |
🎆 |
It would be awesome if the CLI could be moved to click, are there any current technical limitations?
The text was updated successfully, but these errors were encountered: