====== What would git do? ======

It's often nice to be able to check what a command //would// do if you were to run it, but without actually letting it do anything.

This page is basically a summary of how you get around the disappointing fact that almost all git commands have no "dry-run" option.  There are so many ways in which a pretty recently-developed set of tools such as git could be __so__ much better if only the developers had thought about the shortcomings of the commands they were already familiar with, and picked out the best bits, instead of just making the same mistakes all over again (along with, to be fair, a few new ones).

A single consistent "--dry-run" option for all git commands would be a wonderful feature.

===== So, what does git think would happen if I were to... =====

==== ...just keep on editing files locally? ====

<code>git status</code>
  * will tell you about untracked files (which you need to //git add// if you want them under version control) and deleted files (which you should //git rm// unless it was a mistake to delete them).
==== ...do a commit? ====

<code>git diff</code>
  * will show you details of the differences between current files and the last commit.
<code>git diff --cached --name-only</code>
  * will just list the files and not show anything about the differences in their contents.
<code>git diff --cached --name-status</code>
  * apparently does the same thing.
==== ...do a push? ====

This one is an exception.  It **does** have a "--dry-run" option!
<code>git push --dry-run</code>

==== ...do a pull? ====

Firstly, don’t //pull//.  Do a //fetch//, possibly followed by a //merge// or (far better if you can) a //rebase//.  Part of the reason for not //pull//ing is that you can do things in between the //fetch// and the //rebase//, such as finding out what would get changed if you went ahead with the second command.
If the //fetch// tells you that your copy of the repository can be "fast-forwarded", then you can do a //rebase// (simpler) rather than a //merge// (more complex).

To get a list of the files which would be changed (added, deleted, modified, renamed):
<code>git fetch
git diff --name-status @..@{u}</code>

To get a list of the commit comments:
<code>git fetch
git log --oneline ..@{u}</code>

If you're happy with the results, you can then go ahead with a
<code>git rebase</code>
or
<code>git merge</code>
as appropriate.

----
[[.:|Go up]]\\
Return to [[:|main index]].