Skip to content

GitButler can not initialize workspace on empty repositories #8119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
reld opened this issue Apr 11, 2025 · 2 comments
Open

GitButler can not initialize workspace on empty repositories #8119

reld opened this issue Apr 11, 2025 · 2 comments
Labels
bug Something isn't working V3 The ominous upcoming major release should address this issue, eventually

Comments

@reld
Copy link

reld commented Apr 11, 2025

Version

0.14.16

Operating System

macOS

Distribution Method

dmg (Mac OS - Apple Silicon)

Describe the issue

Dear gitbutler team,
first of all THANK YOU!
Love GitButler <3

Today I tried to clone a new repository and got this error:

Unhandled exception
A promise had an unhandled exception.
Error: Reference 'refs/heads/main' not found; class=Reference (4); code=UnbornBranch (-9)
Image

It seems that when you create a new repo on github and you don't add e.g. a README or License, hence forcing a first commit gitbutler is not able to find the ref to the main branch.
Image

The repo got cloned though, but gitbutler could not initialize the workspace.

So cloning entirely empty repositories does not seems to work.

Many thanks in advance,
Reld.

How to reproduce (Optional)

  1. Create a new repository and do not add a README nor a license so the repo will be entirely empty.
  2. Go to git butler and try to clone the repo.

Expected behavior (Optional)

  1. Clone an empty repository as I would using git on the CLI git clone [email protected]/.....

Relevant log output (Optional)

@reld reld added the bug Something isn't working label Apr 11, 2025
@Byron Byron added the V3 The ominous upcoming major release should address this issue, eventually label Apr 12, 2025
@Byron
Copy link
Collaborator

Byron commented Apr 12, 2025

Thanks a lot for reporting!

I'd expect this to be fixed with the next major release of the application, which is "right around the corner".

@reld
Copy link
Author

reld commented Apr 16, 2025

Nice :)
thank you and have a good one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working V3 The ominous upcoming major release should address this issue, eventually
Projects
None yet
Development

No branches or pull requests

2 participants