Skip to content

feat: Commits tab should default to current worktree branch instead of all branches #620

Description

@Luis-WowApps

Related UX suggestion:
Consider merging the Changes and Commits tabs into one Git tab, similar to Orca.

That combined view could show, in one place:

  • commit message input / Create PR action
  • changed tracked files
  • untracked files
  • files committed on the current branch
  • commits on the current branch

This would make the worktree state easier to understand because users would not need to switch between separate tabs to answer “what is changed, what is untracked, and what is already committed on this branch?”

Orca's layout makes this clearer: the branch summary, working-tree changes, untracked files, committed branch files, and commit list are visible together for the selected worktree.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions