-
Notifications
You must be signed in to change notification settings - Fork 1
Incorrect help messaging after branch at the bottom of the stack has been merged #1299
Open
Description
Describe the bug
When the branch at the bottom of the stack is merged and the stackit up or stackit down commands are used, a suggestion to restack is provided that reference non-existent commands.
$ stackit up ⮑ new-bottom-branch Checked out new-bottom-branch. The downstack branch old-bottom-branch has fallen behind main - you may want to stackit stack restack.
stackit down ⮑ old-bottom-branch Checked out old-bottom-branch. This branch has fallen behind main - you may want to stackit upstack restack.
To reproduce
- Create a new base stack on main, make a minor change.
- Create a new stack on the base stack and make another minor change.
- Submit the stacks
- Merge the bottom stack in
- Fetch main
git fetch origin main:main - From the top of the stack run
stackit down - From the bottom of the stack run
stackit up - The suggestions in the previous section will be displayed
Run the following:
$ stackit stack --help Error: unknown command "stack" for "stackit" Did you mean this? restack state track Run 'stackit --help' for usage.
$ stackit upstack --help Error: unknown command "upstack" for "stackit" Did you mean this? restack Run 'stackit --help' for usage.
Expected behavior
The help commands either perform the desired action or that the suggested commands exist
Actual behavior
The commands references subcommands that do not exist
Environment
- CLI version: stackit version 0.19.2
- Shell: zsh
- Install method: brew
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.