Skip to content

Clarify lock command usage#373

Closed
GreyforgeLabs wants to merge 1 commit into
CortexLM:mainfrom
GreyforgeLabs:fix-lock-usage-order
Closed

Clarify lock command usage#373
GreyforgeLabs wants to merge 1 commit into
CortexLM:mainfrom
GreyforgeLabs:fix-lock-usage-order

Conversation

@GreyforgeLabs
Copy link
Copy Markdown

Summary

  • add explicit usage forms for cortex lock so the default session-id mode and subcommand mode are not shown as [SESSION_ID] [COMMAND]
  • keep the existing shorthand cortex lock [SESSION_ID] behavior intact

Fixes PlatformNetwork/bounty-challenge#53143

Tests

  • cargo fmt --package cortex-cli --check
  • git diff --check
  • cargo check -p cortex-cli --no-default-features --features cortex-tui
  • cargo run -p cortex-cli --no-default-features --features cortex-tui --bin Cortex -- lock --help

Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@GreyforgeLabs GreyforgeLabs closed this by deleting the head repository May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG][v0.0.7] cortex lock usage signature reverses positional arguments

1 participant