Bug: "git restore --staged" on a newly created repository

Xirui Zhao· May 26, 2020, 06:18 UTC · lore

Tested on git version 2.27.0-rc1 (latest build from master branch on github) and 2.26.2 `git restore --staged file` on a newly created repository outputs error "fatal: could not resolve HEAD", but `git reset file` correctly unstages the file.

Jeff King· May 27, 2020, 07:32 UTC · re: Xirui Zhao · lore

Re: Bug: "git restore --staged" on a newly created repository

On Tue, May 26, 2020 at 02:18:34PM +0800, Xirui Zhao wrote:

> Tested on git version 2.27.0-rc1 (latest build from master branch on github) and 2.26.2
> `git restore --staged file` on a newly created repository outputs
> error "fatal: could not resolve HEAD", but `git reset file` correctly
> unstages the file.

Yeah, "restore" is based on git-checkout, which is a little pickier than "git reset" here. I don't think this ever worked in any version of git-restore. It would probably be OK for it to use the empty tree when HEAD is unborn, at least when operating in git-restore mode.

-Peff