You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATM we run git diff-index without --cached. This gives us all changes. In most cases we can tell if something is staged, because a non-Nonegitsha property is reported.
The one (?) exception are deletions. These have no gitsha property (of course), and only a git diff-index --cached would reveal their potential unstaged nature.
This appears to be the last aspect that prevent next-status from reporting index state. Here is what this looks like in a local draft (the plus-character indicates "staged"):
The text was updated successfully, but these errors were encountered:
ATM we run
git diff-index
without--cached
. This gives us all changes. In most cases we can tell if something is staged, because a non-None
gitsha
property is reported.The one (?) exception are deletions. These have no
gitsha
property (of course), and only agit diff-index --cached
would reveal their potential unstaged nature.This appears to be the last aspect that prevent
next-status
from reporting index state. Here is what this looks like in a local draft (the plus-character indicates "staged"):The text was updated successfully, but these errors were encountered: