[Bugs] I asked Copilot to check out another engineer's pull request and make changes...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😔
**Category:** Bugs
I asked Copilot to check out another engineer's pull request and make changes, but I want to push my changes back on a separate branch/PR.
I requested that Copilot create a PR on a new branch, which it did using the `gh` CLI. When I asked it again to use the built-in tools so the tracking in the app updated to track/display the new PR, it made several tool calls and believed it had updated the state, but nothing appeared to change in the UI.
Ideally, changing the PR or branch a session is tracking would be easy to accomplish via either the UI or a tool call.
---
| Field | Value |
| --- | --- |
| App version | 0.2.33 |
| OS | macOS 26.4.1 |
| Theme | Selene Selenized |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
Research direction
Start in the /chat experience and reproduce the flow: check out an existing pull request, create a separate branch or PR with the gh CLI, then ask the built-in tools to update the tracked PR. Compare the session state with what the UI displays and verify that changing the tracked branch or PR is reflected in the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100