Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[bug] when i start a new session in a branch that has been commited and PR'd, the s...

Open
#4,011 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
git

Research direction

Start by reproducing the issue in the /chat path after committing and PR'ing a branch, then compare the app's Changes area with git status and VS Code's change control pane. Done means a clean branch does not show stale changes, and the Changes area updates when new edits are made.

Written by the indexing model from the issue text.

Description

when i start a new session in a branch that has been commited and PR'd, the session still see's (changes +-) and if i click on it, it showes me changes i guess from the last PR instead of the clean state, if i do a git status, it is 'all up to date' however i do not have 1200 lines of code changes. the (changes) area does update at some point when we start changing code again, but (changes) is almost always out of date. i also have to go to vscode and look at the 'change control' pane to figure out what is 'really' changed. Please fix this.


Field Value
App version 1.1.22
OS Windows 10.0.17763
Theme GitHub
Path /chat
Tenure Week 7
Image
Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/app

All issues in github/app

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.