cargo-crev: Can't commit or pull reviews: UnbornBranch

BTW, instead of instructing users to create a new repo from scratch, you could suggest using forking a template, such as:

https://github.com/dpc/crev-proofs/fork

(of course maybe not this particular url).

The fork UI gives a properly-named, initialized repo, in 1 click.

@kornelski The forking idea has a great side-benefit: we get a list of people who clicked the button! https://github.com/crev-dev/crev-proofs/network/members

I moved to github organization, created a template repo and updated documentation to use one-click forking. Additional benefit - you can can get a list of forks.

The most likely way to hit this is when skimming the instructions at: https://github.com/dpc/crev/blob/master/cargo-crev/src/doc/getting_started.md#creating-a-crevid and overlooking:

Note: cargo-crev requires the master branch to already exist, so the repository you have created has to contains at least one existing commit.

Github is happy to create an uninitalized/commitless repository through https://github.com/new if you don’t select any of these options (and why would you?):

• Initialize this repository with a README
• Add .gitignore
• Add a license

Then, since cargo crev new id doesn’t appear to do sanity checking to catch this, you end up in this state when you try to start using cargo crev trust. Manually creating a commit, deleting %APPDATA%\crev, and rerunning cargo crev new id fixes the issue.

I looked more into it, and I’m not sure if this is worth handling. I mean - this repo did not have HEAD set so technically was in invalid state. I don’t think it’s worth complicating things, just to try to recover from states that should not be there in the first place. If crev left it in the incorrect state - that’s a bug to fix.

@kornelski $HOME/Library/Application Support/? We’re using https://docs.rs/app_dirs/1.2.1/app_dirs/