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
Staged changes are shown above unstaged changes. That's not the logical order. Unstaged changes can modify staged changes (see screenshot) but not the other way around. It's just like a newer commit can modify text added by an older commit. New commits are shown above old commits, so it's logical to follow that pattern for local changes.
To look at it another way, staged changes are closer to the commits. It's trivial to commit staged changes only - it's the default git commit behavior. It's much trickier to commit unstaged changes and omit staged changes, especially if both affect the same file. Thus staged changes should be closer to commits, i.e. lower.
The text was updated successfully, but these errors were encountered:
proski
changed the title
Unstaged changes should be shown above stages changes
Unstaged changes should be shown above staged changes
Feb 23, 2015
Staged changes are shown above unstaged changes. That's not the logical order. Unstaged changes can modify staged changes (see screenshot) but not the other way around. It's just like a newer commit can modify text added by an older commit. New commits are shown above old commits, so it's logical to follow that pattern for local changes.
To look at it another way, staged changes are closer to the commits. It's trivial to commit staged changes only - it's the default
git commit
behavior. It's much trickier to commit unstaged changes and omit staged changes, especially if both affect the same file. Thus staged changes should be closer to commits, i.e. lower.The text was updated successfully, but these errors were encountered: