Dry run option

The mane problem is there are no confirmations when git destroys data. It desperately needs a dry run, read only, or a prompt before erase like every other sane program.

Merge that works

Why oh why can't a single merge tool actually merge anything to this day?  Surely Nvidia's $2 tril valuation is based on AI merge tools solving all our problems.

Show what is being compared in a diff

It shows a or b in a text console or some garbage filename in a meld window instead of anything about what side corresponds to what diff argument.

Show new files in a diff

git diff doesn't show what files were added or deleted

Label stashes something more useful than stash@{0}

Stashes are like commits without any way to document.  You have to git stash apply, then git stash save "comment" to add a comment.

Show the branch history in the log

What branch did a commit come from so we know what branch to merge into?

English translations

Git communicates in some kind of Greek Finnish dialect.  Reflog, rev-parse, stash, squash, fetch, pull need to be translated into standard words used by all the repo managers.

The lion kingdom made a growing list of translations for git's strange dialect of finnish.

Consistent paths

Git status gives relative paths from the working directory.

Git checkout gives absolute paths from the top level.  Why Linus?  Why?

Consistent scrolling

Git status prints to stdout with no scroll buffer

Git diff prints to an instance of the pager program so you can scroll back.  

In the continuing shortcomings of GIT, the typical workflow involves "pulling" a "remote" repository with your own, followed by a conflict.  

$ git status
rebase in progress; onto 4166110
You are currently rebasing branch 'master' on '4166110'.

Would it kill git to show what remote repository master is in & the top level of the repository of the error like Makefiles used to?