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
{{ message }}
This repository was archived by the owner on Jan 7, 2026. It is now read-only.
I tried 3-4 times the Github copilot remote agent and never with satisfactory results. here is one
Describe your experience
I wanted to hand over a change to github copilot remote from a already forked branch. It made some changes and created a PR. It could not test the fastapi app due to firewall and probably redis server.
Using the interface I could not select the branch merged into. and before I saw it I got a merge commit in the main branch. I asked Copilot to revert and to add the merge commit to the source branch, but it could not resolve the git hostory also the branch was already deleted. even if I did not clicked on delete.
Suggestions for improvement
Ideally I would like that the remote agent makes the changes accessible in a discussion. that it is easy to continue working on it. e.g. even with the self-discussion it had.
In this case I would have just run the test locally.
Alternatively, make a fully remote agent. but not as a continuation of a chat history. e.g. like seting up a new workspace.
Let the user describe the changes to made, ask some pre-flight questions and then make the PR.
I tried 3-4 times the Github copilot remote agent and never with satisfactory results. here is one
Describe your experience
I wanted to hand over a change to github copilot remote from a already forked branch. It made some changes and created a PR. It could not test the fastapi app due to firewall and probably redis server.
Using the interface I could not select the branch merged into. and before I saw it I got a merge commit in the main branch. I asked Copilot to revert and to add the merge commit to the source branch, but it could not resolve the git hostory also the branch was already deleted. even if I did not clicked on delete.
Suggestions for improvement
Ideally I would like that the remote agent makes the changes accessible in a discussion. that it is easy to continue working on it. e.g. even with the self-discussion it had.
In this case I would have just run the test locally.
Alternatively, make a fully remote agent. but not as a continuation of a chat history. e.g. like seting up a new workspace.
Let the user describe the changes to made, ask some pre-flight questions and then make the PR.