Describe the bug
When you issue work to co-pilot via the /delegate command, it seems to disregard whatever you ask of it in terms of what branch it should work from. If I specify, please take a branch of the current branch I'm on, or please take a branch from 'integration' and call it 'banana', it disregards that and branches from the default (master) branch with whatever name it fancies.
It would be nice if it either listened or had some specific post '/delegate' prompts like 'what source branch would you like to use ', and 'what would you like to call the new branch'?
Affected version
GitHub Copilot CLI 1.0.27
Steps to reproduce the behavior
- Type '/delegate Make this app say 'hello world' in the console. Please branch from the 'development' branch and NOT master, call your branch 'hello'.
- Watch it ignore you (assuming your repo is set up with default branch 'master'), and branch from master anyway
Expected behavior
It should branch from at least the branch you're on when you call the 'delegate' command, and ideally allow you to specify.
Additional context
No response
Describe the bug
When you issue work to co-pilot via the /delegate command, it seems to disregard whatever you ask of it in terms of what branch it should work from. If I specify, please take a branch of the current branch I'm on, or please take a branch from 'integration' and call it 'banana', it disregards that and branches from the default (master) branch with whatever name it fancies.
It would be nice if it either listened or had some specific post '/delegate' prompts like 'what source branch would you like to use ', and 'what would you like to call the new branch'?
Affected version
GitHub Copilot CLI 1.0.27
Steps to reproduce the behavior
Expected behavior
It should branch from at least the branch you're on when you call the 'delegate' command, and ideally allow you to specify.
Additional context
No response