Skip to content

Conversation

@puqeko
Copy link

@puqeko puqeko commented Jan 28, 2024

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.
  • Update plugins with new status.

Tested on darwin-x86 only.

Thank you for this work. An inspirational read.

Treat an unreadable index as if option to ignore index computations was
passed. Instead of reporting no-repo, basic repo info will be reported.
Add 30th entry to response which is 1 if index computations are disabled
OR the index cannot be read, 0 otherwise. The requester, knowing the requests
contents, can determine if the index could not be read while still receiving
repository information that is avaliable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant