Breaking Down [BUG] [alpha] AddWorktreeDialog

When git branches fail in AddWorktreeDialog, the real flaw isn’t just the code - it’s silence. A network timeout or broken repo triggers silent console errors, but the UI remains eerily empty. No alert, no retry, no clue. The loading spinner lingers, then vanishes - like the branch never existed. This isn’t just a minor glitch; it’s a UI betrayal. Studies show users expect feedback in workflows - even for tech stumbles. Here is the deal: a missing error message leads to confusion, missed retries, and lost trust.

Branches appear empty, but the real silence is the fetch call at line 91 that catches an error yet does nothing visible. Users don’t know if the repo is broken or their connection failed.

Psychologically, this triggers anxiety - users assume the repo is fine when nothing loads, or they’re simply out of luck. The lack of transparency turns a simple branch load into a silent failure, affecting perceived reliability. Think of it like a restaurant taking orders but never confirming receipt - frustrating and distrustful.

Hidden in plain sight: this isn’t a bug in isolation. Git workflows thrive on feedback; silence erodes confidence. Many modern tools, like GitHub’s branch pickers, now show ‘Failed to fetch branches’ modals with retry buttons. But here, the user is left guessing.

Safety first: always show errors, not just logs. If a branch fetch fails, display a clear message, log the issue, and offer a retry. Don’t bury failure in silence.

The bottom line: in tech, visibility is trust. Let users know when things go wrong - and give them a way to fix it.