Less of a serious PR and more of a question, if the index is unreadable (ie core.splitIndex is enabled) then why does gitstatus report no repo? It means that a command prompt won't show any information where it would have otherwise if the 'ignore index computations' option was given. Wouldn't it be a better user experience if we fall back to that instead?
Changes
Respond as if index computations are ignored in the case reading the index fails, instead of reporting no repo.
Append entry 30 in response, set if the index was not read, so that this failure can be detected should we wish.
Less of a serious PR and more of a question, if the index is unreadable (ie
core.splitIndexis enabled) then why doesgitstatusreport no repo? It means that a command prompt won't show any information where it would have otherwise if the 'ignore index computations' option was given. Wouldn't it be a better user experience if we fall back to that instead?Changes
Tested on darwin-x86 only.
Thank you for this work. An inspirational read.