-
Notifications
You must be signed in to change notification settings - Fork 37
fix: remove deprecated --hard flag and all references #371
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -425,7 +425,7 @@ func displayLsResetBreadCrumb(t *terminal.Terminal, workspaces []entity.Workspac | |
| } | ||
| } | ||
| if foundAResettableWorkspace { | ||
| t.Vprintf("%s", t.Yellow("If this problem persists, run the command again with the --hard flag (warning: the --hard flag will not preserve uncommitted files!) \n\n")) | ||
| t.Vprintf("\n") | ||
|
||
| } | ||
| } | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,10 +25,10 @@ recreate a workspace with the name `naive-pubsub` | |
|
|
||
| ``` | ||
| $ brev recreate payments-frontend | ||
| Starting hard reset 🤙 This can take a couple of minutes. | ||
| recreating 🤙 This can take a couple of minutes. | ||
|
|
||
| Deleting workspace - naive-pubsub. | ||
| Workspace is starting. This can take up to 2 minutes the first time. | ||
| Deleting instance - naive-pubsub. | ||
| Instance is starting. This can take up to 2 minutes the first time. | ||
|
||
| name naive-pubsub | ||
| template v7nd45zsc Admin | ||
| resource class 4x16 | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reset breadcrumb now prints only a blank line when a resettable instance is found. Since
--hardwas removed, this would be a good place to replace the old guidance with an actionable next step (e.g., suggestbrev recreate <name>ifbrev resetdoesn’t resolve the issue) rather than emitting an empty line.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intentionally left blank. The prior --hard breadcrumb caused a production incident (nemoclaw-f4a386 / BREV-9066 / the thread in #ep-brev-support) because an AI coding agent auto-executed the destructive suggestion. brev recreate is equally destructive (delete + create), so suggesting it from ls output re-introduces the same vector. Users who need a recreate can discover it via brev --help or docs, which requires a deliberate action rather than reading ls output.