docs(workon): clarify -c flag usage and exclusivity
Some checks failed
CI / Test (push) Successful in 33s
CI / Lint (push) Successful in 25s
CI / Build (push) Has been cancelled

Updated the usage string to show -c as an alternative option and added a note
that it cannot be used with other flags.
This commit is contained in:
Gregory Gauthier 2026-03-31 15:12:50 +01:00
parent 5f864307b8
commit d752a73742

View File

@ -23,7 +23,7 @@ Also, if no IDE is specified in the config, the feature will default to not open
**Usage**: **Usage**:
``` ```
grokkit workon <todo_item_title> [-m '<custom_commit_message>'] [-f] grokkit workon <todo_item_title> [[-m '<custom_commit_message>'] [-f]] | [-c]
``` ```
**Arguments**: **Arguments**:
@ -36,7 +36,7 @@ grokkit workon <todo_item_title> [-m '<custom_commit_message>'] [-f]
- `-f`: This signifies a "fix" rather than a todo item (the default is always a todo item) - `-f`: This signifies a "fix" rather than a todo item (the default is always a todo item)
- `-c`: "completes" the work item. This means: - `-c`: "completes" the work item (note: cannot be used with other flags). This means:
- If it is a todo, it will be moved to the "completed" folder, and the index readme will be updated. - If it is a todo, it will be moved to the "completed" folder, and the index readme will be updated.
- If it is a fix, the work plan will be moved to the "completed folder". No index update is necessary. - If it is a fix, the work plan will be moved to the "completed folder". No index update is necessary.
- In either case, the update will be committed to the branch. - In either case, the update will be committed to the branch.