You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GitHub Copilot App automatically commits. I would like to have a feature setting to turn that off
What problem are you trying to solve?
Context: I'm used to do commits manually in Git. While testing out the GitHub Copilot app, I noticed that the default behaviour seems to be that after "I am finished" is detected, the changes are commited. Unfortunately, I did not get a chance to review the changes.
In my case, I had it scan my customer facing documentation to search for gaps between the documentation and my memory bank. The update worked well, but I still wanted to iron out some changes. After writing "Please change sentence A to sentence B", I noticed another commit.
After writing "Don't do Git commits yourself. I need to manually say okay before you make a commit" the behaviour was as I wanted it. Then, I manually gave my go ahead.
Would it be possible to have either
a general setting regarding commits
a toggle somewhere in the prompt area like "allow auto-commits" that I can turn on/off in the session?
Feature summary
The GitHub Copilot App automatically commits. I would like to have a feature setting to turn that off
What problem are you trying to solve?
Context: I'm used to do commits manually in Git. While testing out the GitHub Copilot app, I noticed that the default behaviour seems to be that after "I am finished" is detected, the changes are commited. Unfortunately, I did not get a chance to review the changes.
In my case, I had it scan my customer facing documentation to search for gaps between the documentation and my memory bank. The update worked well, but I still wanted to iron out some changes. After writing "Please change sentence A to sentence B", I noticed another commit.
After writing "Don't do Git commits yourself. I need to manually say okay before you make a commit" the behaviour was as I wanted it. Then, I manually gave my go ahead.
Would it be possible to have either
Proposed solution
No response
Workflow impact
No response
Installation context
No response
Additional context
No response