This usually happens when your feature branch was created from an outdated version of dev, or if dev was updated (via a squash merge or rebase) after you started your work. GitHub’s UI shows the 'diff' between the common ancestor of both branches and your current head.

If those changes are already in dev but appearing in your PR, it means your branch doesn't 'know' they are already there. Here is how to fix it:

1. Update your local environment
   First, ensure your local dev is perfectly synced with the remote:

git checkout dev
git pull origin dev

2. Sync your feature branch
   Go back to your PR branch and bring in the latest changes from dev. You have two options:

Option A: Merge (Safest)

git checkout your-feature-branch
git merge dev

This will create a merge commit, but it should clear the 'already merged' changes from the GitHub UI.

Option B: Rebase (Cleaner history)

git checkout your-feature-branch
git rebase dev

This rewrites your commits on top of the current dev. Note: You will need to git push --force after this.

If your team uses Squash and Merge, the commit IDs change when they land in dev. Even if the code is the same, Git sees different hashes and thinks they are 'new' changes you are trying to introduce. Syncing your branch as shown above forces Git to realize those changes are already part of the target branch's history.

Run these commands on your feature branch to sync with latest dev

git checkout your-feature-branch
git fetch origin
git rebase origin/dev
git push origin your-feature-branch --force-with-lease

This rebases your branch onto latest dev and force pushes. PR will update to show only your changes.

Most likely cause: your branch isn’t fully up to date with dev, even if the changes were already merged there.

GitHub compares branches by commit history.
If your branch doesn’t contain the latest dev commits (or if dev was rebased/force-pushed), GitHub will show already-merged changes as “new” in your PR.

Quick fix:

git fetch origin
git rebase origin/dev   # or: git merge origin/dev
git push --force-with-lease  # only if you rebased

Also double-check your PR is targeting the correct base branch (dev).

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬