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.

Sign up for GitHub

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

Jump to bottom

Implement the nuke subcommand #110

Open
RadicalZephyr opened this issue Dec 31, 2015 · 2 comments
Open

Implement the nuke subcommand #110

RadicalZephyr opened this issue Dec 31, 2015 · 2 comments
Labels
to-do
Milestone
1.0

Comments

@RadicalZephyr
Copy link
Collaborator

This totally removes a shell. Git directory and all. Probably should always prompt whether to proceed with a message explaining what it does. No default behavior if no shell name is given.

Potential addition. If user tries to nuke the current shell, offer to switch shells like git does? There's no real concept of a "main" or "master" shell though...
@RadicalZephyr RadicalZephyr modified the milestone: 1.0 Dec 31, 2015
@RadicalZephyr RadicalZephyr mentioned this issue Dec 31, 2015
Closed
@RadicalZephyr
Copy link
Collaborator Author

One nice safety feature that we could add is to try and determine if the shell-to-be-nuked has any git history that hasn't been pushed to a remote. This would be a post 1.0 enhancement though.

@reillysiemens
Copy link
Collaborator

Uhh... yes. We should totally do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to-do
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
2 participants
@RadicalZephyr @reillysiemens