Skip to content

Can we deny changes without exiting prompt? #602

@isaacnboyd

Description

@isaacnboyd

Describe the feature or problem you'd like to solve

When I ask copilot to make a lot of changes, sometimes I don't want them all.

Proposed solution

Hello,

When I ask copilot to do something, like "Please fix all the spelling mistakes in markdown files within this repository", it does a great job. Thanks copilot.

Except sometimes it makes suggestions I don't want. And when that happens, my options are:

   1. Yes
   2. Yes, and approve all file operations for the rest of the running session                                                                                            
   3. No, and tell Copilot what to do differently (Esc)  

When I say "No", I'm sent back to the copilot terminal. And then I have to kind of start over.

Wouldn't it be nice if copilot behaved like git add -p where I can say "no" and it moves on to the next change:

(1/3) Stage this hunk [y,n,q,a,d,j,J,g,/,e,p,?]? ?
y - stage this hunk
n - do not stage this hunk
q - quit; do not stage this hunk or any of the remaining ones
a - stage this hunk and all later hunks in the file
d - do not stage this hunk or any of the later hunks in the file
j - leave this hunk undecided, see next undecided hunk
J - leave this hunk undecided, see next hunk
g - select a hunk to go to
/ - search for a hunk matching the given regex
e - manually edit the current hunk
p - print the current hunk, 'P' to use the pager
? - print help

This is a little much ^ but I think that a "yes, yes all, no, no all" would be amazing.

-Isaac

Example prompts or workflows

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions