Skip to content
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

[ENH] - Order Nebari commands in CLI more consistent with the order of their use #2846

Closed
Adam-D-Lewis opened this issue Nov 11, 2024 · 4 comments
Labels
good first issue Good for newcomers

Comments

@Adam-D-Lewis
Copy link
Member

Adam-D-Lewis commented Nov 11, 2024

Feature description

As you can see commands are ordered destroy, deploy, init, info. That is roughly opposite of what I'd like since the first command teh user does is init or info, then deploy, then destroy.
image

Value and/or benefit

More intuitive UX

Anything else?

No response

@Adam-D-Lewis Adam-D-Lewis added the good first issue Good for newcomers label Nov 11, 2024
@Adam-D-Lewis Adam-D-Lewis changed the title [ENH] -Order Nebari commands in CLI more consistent with the order of their use [ENH] - Order Nebari commands in CLI more consistent with the order of their use Nov 12, 2024
@kernel-loophole
Copy link
Contributor

@Adam-D-Lewis this issue is fixed in this PR #2916

@Adam-D-Lewis
Copy link
Member Author

I saw that. Thanks for doing that! FYI, I expect to be able to review your PR next week.

@Adam-D-Lewis
Copy link
Member Author

Oh, looks like Chuck already reviewed and merged. I'll close this. Thanks again @kernel-loophole !

@github-project-automation github-project-automation bot moved this from New 🚦 to Done 💪🏾 in 🪴 Nebari Project Management Jan 23, 2025
@kernel-loophole
Copy link
Contributor

@Adam-D-Lewis no problem ,any other issues which are still in progress or need any enhancement would to work on it .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Done 💪🏾
Development

No branches or pull requests

2 participants