DEV Community

Cover image for I built a VS Code start page for my Git repositories

I built a VS Code start page for my Git repositories

Emanuele Bartolesi on November 18, 2026

I open VS Code and have to decide which repository to open first. I know which ones I've been working on. What I can't always remember is where I l...
Collapse
 
diazisme profile image
Manuel Diaz •

That sounds good

Collapse
 
kameh0use profile image
Omer Cihangiroglu •

Awesome!

Collapse
 
amintacccp profile image
tamina •

The worktree grouping is the detail that sold me — a clean main checkout sitting next to a linked worktree with unfinished edits is exactly where I lose track. Do you find the 'With changes' filter or the pinned section does more of the daily work for you?

Collapse
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

Yes, I am using a lot "with changes", especially when I use agents from Claude or GitHub Copilot and sometimes they don't commit the files.

Collapse
 
amintacccp profile image
tamina •

Thanks for answering! That makes total sense — agents leave uncommitted edits behind all the time, so "with changes" is the most direct place to look when you're wondering what the agent actually touched. Pinned feels more like the long-term anchor for the repos you keep coming back to. The split between the two is clear now.

Thread Thread
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

yes, I pinned my top repos that I use more or less every day.

Thread Thread
 
amintacccp profile image
tamina •

Makes total sense — the daily-driver repos earn the pin. Do you find the set stays pretty stable, or does it rotate a lot as projects come and go? I keep ending up re-pinning whenever I switch focus, which is half the reason I started thinking about better ways to organize starred repos.

Thread Thread
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

I switched the pinned more or less every two weeks.

Collapse
 
sylwia-lask profile image
Sylwia Laskowska •

Wow, how cool is that!!!

Collapse
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

Thanks! Of course it's opensource, so if you want to collaborate or just add issues or whatever, you are more than welcome :)

Collapse
 
steven_mock_afbb801174fc3 profile image
Steven Mock •

What I check first is exactly what this answers: uncommitted changes, then unpushed commits, then whether an agent left a worktree behind. I switch between projects a lot building Homeowner HQ for realtors and lenders, launching December 4 on Amazon AWS, and the worst way to start a morning is opening a repo and finding out later that yesterday's work was never pushed — or that an agent's worktree has edits I forgot about. Seeing ahead/behind counts before opening the folder is the part I would use every day. The pinned repos and the quick switcher are a bonus. Installing it today.

Collapse
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

I also created the standalone version of the extension: github.com/kasuken/repoboard

Collapse
 
the_daily_flare profile image
The daily flare •

I think seeing git status before opening a repo would save me a lot of guessing.

Collapse
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

this is why I created this extension!
I am also creating a stand alone application.

Collapse
 
anshikaguleria profile image
Anshika Guleria •

This is a life saver

Collapse
 
kasuken profile image
Emanuele Bartolesi Playful Programming •

Thank you very much.
If you have any feedback, please share with me or use the issues on the repo. 🙂