keybase / keybase/client

Mac team git repos "warning: remote HEAD refers to nonexistent ref, unable to checkout"

Open
#25,345 2 comments 2 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

I have tried creating new teams, as well as new git repos both via the UI and the CLI. When I push to the repo I get the following:

```bash
Initializing Keybase... done.
Syncing with Keybase... done.
Counting objects: 854 bytes... done.
Preparing and encrypting objects: (100.00%) 854/854 bytes... done.
Counting refs: 41 bytes... done.
Preparing and encrypting refs: (100.00%) 41/41 bytes... done.
To keybase://team/benniemosher_dev/secret-store
* [new branch] main -> main
```

Then when I try to look at the files in the Keybase UI, it is empty. I then try to clone the repo under a different folder name and get this error:

```bash
Cloning into 'secret-store-again'...
Initializing Keybase... done.
Syncing with Keybase... done.
Counting: 854 bytes... done.
Cryptographic cloning: (100.00%) 854/854 bytes... done.
warning: remote HEAD refers to nonexistent ref, unable to checkout
```

I have uninstalled the keybase app, and run `keybase git gc` on the repos, but nothing seems to make the files stay in the repo after the first push. This is making Git unusable. Can you please assist?

my log id: ed436db9ee590a6306443e1c

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported flow: create a team repository, push the main branch, inspect it in the Keybase UI, and clone it elsewhere. Compare the repository's remote HEAD with the pushed main ref; done means the UI shows the files and a fresh clone checks out the expected branch without the warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.