Issue Summary

When navigating between repositories and viewing the Commits tab, the UI shows a commit and branch from a different branch context. It appears to affect repositories that have more than one branch.

From the investigation, this appears to be a navigation/state bug: switching repositories/branches causes the commit view to display the wrong branch within the same repository, and then incorrectly resets the branch selection on navigation.

Steps to Reproduce

1. Open repository RepositoryA.
2. Ensure the BranchA branch (the main branch for this repo) is selected.
3. Open the Commits tab and note the commit list and the main commit hash for BranchA.
4. Navigate to the RepositoryB repository.
5. Go to the Commits tab for RepositoryB.

Expected Results

When navigating to RepositoryB and opening the Commits tab:

• The branch selector should only show branches that actually exist in RepositoryB.
• The default selection should be BranchB (or that repo’s configured default/main branch).

When navigating back to RepositoryA:

• The branch selection should remain on BranchA (its main branch) or at least not be silently reset to another branch if BranchA is the configured main branch.
• The commit list should stay consistent with the branch explicitly selected by the user.

Actual Results

The Commits tab for RepositoryB shows:

• Branch: BranchA (even though RepositoryB does not have a BranchA branch).
• The commit shown is from a completely different branch than RepositoryB’s BranchB.

When navigating back to RepositoryA:

• The branch selection is reset to BranchB (or main, depending on your setup) instead of staying on BranchA, even though BranchA is the main branch for RepositoryA.
• The commits page now only shows the BranchB/main branch commits, not BranchA.

Workaround

Workaround is to open the commit tab in a new window instead of switching them using the navigation.