Introducing the New GitLens Home View in GitLens 16

[justinrobots]

In GitLens 16, we’ve reimagined the GitLens Home View (accessible via the GitLens icon in the VS Code activity bar) to better guide you through your development workflows. This updated experience is now available in the GitLens pre-release and can be enabled in Settings with: "gitlens.home.preview.enabled": true.

The new Home View is designed to help you answer three key questions throughout your day:

• What am I actively working on now?
• What do I need to work on next?
• What have I worked on recently?

What am I actively working on now?

The **ACTIVE** section shows your current repository and branch, alongside the repository state and actions for syncing (push, pull, fetch), switching repos/branches, and viewing working directory changes.

If your branch is tied to a pull request or issue, GitLens surfaces those details so you can check PR status, continue reviews, or revisit issue specs. GitLens will also guide you to start a PR from your current branch if it can't find one.

💡 Connect integrations to view pull request and issue information in GitLens

What do I need to work on next?

The **LAUNCHPAD** section unblocks you and your team by showing pull requests that need your review, are blocked, or are ready to merge. Quickly jump to PRs to review, comment, or merge.

With the new Start work action, you can easily begin a new branch or worktree, or generate one from an existing issue.

What have I worked on recently?

The **RECENT** section lets you quickly return to previous work by showing recent branches, worktrees, and PRs with activity for your chosen timeframe.

---

We’d love your feedback on this new experience—try it out and let us know what you think!

[fmabid]

I was using GitLens's classical look. Now, after switching to the new version, I am a little lost.

I have two questions:

1. How do we merge a remote into the current branch locally?
2. Where do find/get the list of all remote branches?

[justinrobots]

Hi @fmabid the Remotes view was moved into a consolidated GitLens view in Source Control. It can be restored to its original position from the menu in that new view. More about that change in this discussion.

Does locating the Remotes view answer the first part of your question?

[fmabid]

@justinrobots yeah, thanks.

[evenkov]

The new Home View is as everything new a bit confusing. So I have lost in working in Worktrees. Here is my confusion:
I have two worktree(default - working branch, and second quick fix). On new Home View when I'm working on default I can see the quick fix one. There is no option from here to open it in new window by Alt+Click.

After I switch to worktree quick fix in Home View I cannot return to my default one. It shows me only branch for default worktree

So the only way to switch back to default worktree is from Command Palette ->GitLens: Git Open Worktree...

The other way I can switch to worktree is from GitLens tab in Source Control. There is a option to open Worktree in New Window with Alt + Click

Maybe that's concept in new Home View or?

EDIT:
So after all day working on several worktree I think I understood: the default is my branch work directory and all other are copies/worktrees. So it is correct shown as branch, not worktree. The problem is than if I open some worktree in same window of VSCode then I cannot return/switch to branch to default one!

[justinrobots]

Hi @evenkov thanks for the feedback!

1. GitLens views like Worktrees were moved into a consolidated GitLens view in Source Control. You can easily restore them to their previous locations or move them wherever you want. More on that change in this discussion.
2. The default worktree showing as a branch in the new Home instead of a worktree is a bug. We're on it!

#3764

[evenkov]

Thanks!
I'm getting used with Home View and in general I like the idea.
I after I wrote this I found discussion and now used GitLens view in Source Control. The idea to combine all this views in one - GitLens is very good and I think most of us will like it!