Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

boxcli: add clean command#2341

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
truearken wants to merge9 commits intojetify-com:main
base:main
Choose a base branch
Loading
fromtruearken:derarken/add-clean-command

Conversation

truearken
Copy link
Contributor

@truearkentruearken commentedOct 9, 2024
edited
Loading

Summary

This if a first draft for#2335, I am not sure about the behaviour or features of the command yet so I only added basic functionality.
The issue also mentioned deleting files like .envrc, I didn't include this yet since these files might be generated by a user instead of the devbox, maybe this should be added by an optional parameter? or are generated files tracked?
I also wasn't sure if the clean command should exit the devbox shell or not. In case it should, is the pid of the devbox saved anywhere so it can be killed, or is there a better way to do so?

How was it tested?

  • devbox init
  • devbox add go
  • devbox shell
  • devbox clean

=> expected result: .devbox, devbox.lock are deleted and the user remains in the shell.

I also included a test, but I can't test it because of#2342 so it might fail.

Edit

The behaviour is as following now:
runningdevbox clean deletes .devbox and devbox.lock
runningdevbox clean --hard asks for a confirmation and also deletes devbox.json

@truearkentruearken marked this pull request as ready for reviewOctober 9, 2024 20:18
@truearken
Copy link
ContributorAuthor

I added the hard flag now to also delete the devbox.json file, I don't quite like the naming yet and am open for suggestions

@trya2l
Copy link

Hi, what about--all, or--force ?

@truearken
Copy link
ContributorAuthor

All might be an option. Imo force is something else, it means perform an action even though it might break things, an doesn't fit the action here.

trya2l reacted with thumbs up emoji

@adamdicarlo0
Copy link
Contributor

How aboutdevbox uninit ordevbox eject?

A command namedclean deletingdevbox.json anddevbox.lock would be very surprising to me.

PascalLeMerrer reacted with thumbs up emoji

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@truearken@trya2l@adamdicarlo0

[8]ページ先頭

©2009-2025 Movatter.jp