**Bug: Changes counter uses stale session baseline after merging main**
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Bug: Changes counter uses stale session baseline after merging main
After merging the latest main into a feature branch, the Changes counter still compares the branch against the baseline captured when the worktree session was created. This causes changes already present on main to appear as part of the feature branch.
The working tree is clean, and a Git diff against the current remote main shows only the feature’s changes. The UI should compare against the current target branch or update its baseline after main is merged.
| Field | Value |
|---|---|
| App version | 1.1.21 |
| OS | Windows 10.0.22631 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 3 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the /chat path by reproducing the Changes counter behavior after merging the latest main into a feature branch. Trace how the session baseline and current target branch are selected, then verify that the counter excludes changes already on main while retaining the feature changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100