Describe the bug
Clicking Clone on a Project whose announcement's clone tag points to a private GitHub HTTPS URL fails with only Couldn't clone repository in the UI. The same URL clones fine from a plain Terminal on the same machine, using the exact same user's credentials.
Root cause looks like the Tauri-spawned git process doesn't inherit the user's system git config (credential.helper=osxkeychain, gh credential integration, etc.) — a well-known macOS gotcha where GUI apps launched from Finder/Dock don't get the interactive shell's env.
Steps to reproduce
- Announce a Project whose
clone tag is a private GitHub HTTPS URL (e.g. https://github.com/<org>/<private>.git)
- On macOS, in Buzz Desktop, click Clone on the announcement
- Observe error:
Couldn't clone repository
- In a Terminal on the same machine:
git clone https://github.com/<org>/<private>.git /tmp/x — succeeds
Expected behavior
Desktop's clone flow should either:
- Inherit the system git credential-helper chain (respect
~/.gitconfig, osxkeychain, gh's helper), or
- Prompt for GitHub credentials / offer to use an existing
gh session, or
- Surface the underlying
git stderr so users can self-diagnose (currently the UI swallows it)
Version and platform
- Buzz Desktop: 0.5.11 (
CFBundleShortVersionString from /Applications/Buzz.app/Contents/Info.plist)
- macOS: Darwin 25.5.0
- Bundle:
xyz.block.buzz.app
Related
Additional context
Public repos on GitHub HTTPS clone fine (no auth needed), so this only bites private repos. SSH URL (git@github.com:...) is a workaround if the user has an SSH key configured in ssh-agent — but same GUI-env issue likely applies there too on macOS unless ssh-agent is loaded system-wide.
Describe the bug
Clicking Clone on a Project whose announcement's
clonetag points to a private GitHub HTTPS URL fails with onlyCouldn't clone repositoryin the UI. The same URL clones fine from a plain Terminal on the same machine, using the exact same user's credentials.Root cause looks like the Tauri-spawned
gitprocess doesn't inherit the user's system git config (credential.helper=osxkeychain,ghcredential integration, etc.) — a well-known macOS gotcha where GUI apps launched from Finder/Dock don't get the interactive shell's env.Steps to reproduce
clonetag is a private GitHub HTTPS URL (e.g.https://github.com/<org>/<private>.git)Couldn't clone repositorygit clone https://github.com/<org>/<private>.git /tmp/x— succeedsExpected behavior
Desktop's clone flow should either:
~/.gitconfig,osxkeychain,gh's helper), orghsession, orgitstderr so users can self-diagnose (currently the UI swallows it)Version and platform
CFBundleShortVersionStringfrom/Applications/Buzz.app/Contents/Info.plist)xyz.block.buzz.appRelated
Additional context
Public repos on GitHub HTTPS clone fine (no auth needed), so this only bites private repos. SSH URL (
git@github.com:...) is a workaround if the user has an SSH key configured inssh-agent— but same GUI-env issue likely applies there too on macOS unlessssh-agentis loaded system-wide.