-
Notifications
You must be signed in to change notification settings - Fork 37
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
Remove the bistro command #241
Comments
Maybe a better suited name would do the trick, something like Adding documentation and stating that it's the default command seems good enough but I think it's already the case for bistro We can't remove it without doing a major release but if we wish to improve the doc and eventually add an alias we can do that already! We could then deprecate it and finally drop it when releasing 2.0! |
@NathanReb Should we move this for the 2.0.0 milestone? I fear that given we already started, it is a bit late to remove but we could at least deprecate it. |
I think it's fine to remove it in 2.0 without warning. Not best practice but I doubt anybody has a script that runs |
Calling
dune-release
without a sub-command is the same as callingdune-release bistro
. Is there really a benefit to having this command? (not sure this is even properly documented)The text was updated successfully, but these errors were encountered: