Changes tab does not update after the session's PR is merged
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
Describe the bug
In the Copilot desktop app (Tauri), a session's Changes tab does not appear to refresh after the session's pull request is merged on GitHub. The tab continues to reflect the pre-merge state instead of updating to the new reality (merged branch / updated base).
Note: this report is about the desktop app UI, not the CLI itself — filed here as the reachable public tracker; please reroute if there is a dedicated app repo.
Affected version
Desktop app ~1.1.14 (inferred from ~/.copilot/data.db.pre-update-backup-1.1.14-*); embedded CLI reports version 1.0.80.
Steps to reproduce the behavior
- Open a worktree-backed project session on a feature branch with changes.
- Create a PR from the session and merge it on GitHub while the session stays open.
- Return to the session and open the Changes tab.
- Observe that the view still shows the pre-merge state; it does not update after the merge.
Expected behavior
After the session's PR merges, the Changes tab refreshes — e.g., recomputes the diff against the updated default branch (or shows an appropriate post-merge state) without requiring manual intervention.
Additional context
- OS: macOS (Darwin, ARM).
- Session type: worktree-backed, branch created and pushed by the session; PR merged via the GitHub web UI.
- Possibly related: inside the session, the branch is not auto-updated after merge either (
git fetch/merge origin/mainhad to be run manually), so the tab may be diffing against a stale merge-base. - Reported by the session's user mid-workflow and relayed by the agent; happy to pull logs (
--log-level/--log-file) if you tell me which ones help.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 Tauri 桌面应用的 Changes 标签页和 session 的 pull-request/branch 更新路径入手,使用报告中的基于 worktree 的 macOS 设置,复现 GitHub 上完成 merge 后视图仍然过时的问题。跟踪标签页何时刷新,以及 merge-base 如何更新;完成标准是标签页显示 merge 后的状态,而不需要手动执行 fetch 或 merge 命令。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- git, github, tauri
- 领域
- desktop
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 48/100