Error: Getting main branch OID for repository

[jacobsimpson-addepar-jenkinsx-bot]

Nice work, I like where you are going with this.

I'm having a little trouble getting it going on one of my repos.

$ git branchless init 
$ git sl
Error: Getting main branch OID for repository

Caused by:
    cannot locate remote-tracking branch 'master'; class=Reference (4); code=NotFound (-3)

I suspect this is happening because my main branch is named main not master.

Now that the repository is git branchless init, branchless error messages are appearing for other commands too:

$ git rebase --onto main 4bfe550 b1
branchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
dropping 05a699a Generate. -- patch contents already upstream
branchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
branchless: processing commit
branchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
branchless: processing 2 rewritten commits
Error: Processing post-rewrite hook

Caused by:
    0: Getting main branch OID for repository
    1: cannot locate remote-tracking branch 'master'; class=Reference (4); code=NotFound (-3)
Successfully rebased and updated refs/heads/b1.

Thank you.

[arxanas]

Will address in more detail later, try git config branchless.mainBranch main

[arxanas]

I suppose this is two issues:

• The error message could be clearer here, and suggest some steps for remediation.
• git branchless init should autodetect the correct branch name (one of the items mentioned in Known issues #1).

I'll see if I can get to this sometime soon.

[jacobsimpson-addepar]

git config branchless.mainBranch main did it. smartlog is now working for me. Haven't tried the others yet.

[sassman]

same issue happens also on a repo that has never been yet pushed upstream (hence has no remote tracking branch)

[arxanas]

I've tried to improve the experience here in #31 by 1) auto-detecting the main branch name, and 2) printing a more actionable, less misleading message. (The error message is complaining that it can't find a remote branch like origin/master, not that it can't find a local remote-tracking branch like master synced to origin/master.)

[arxanas]

Resolved in #31.