Does Git Add have a verbose switch

I am in the process of moving all my private an public repo’s over to github. One of the decisions I have made is to only use the console as it means a smaller tooling footprint if I ever need to change PCs, etc.

I would be a huge user of console applications and being new to git I decided to purchase Tekpub’s Mastering Git series since it shows you how to intergrate git bash as a toolbar.

  • Submission to gerrit fails with “Change is Closed” message
  • Is there an exclude file-equivalent for pushing in git?
  • Convert portable msysGit to full installed equivalent (but still be portable)
  • Best way to send a git repo with uncomitted changes?
  • Azure Web App of nodejs application loads blank screen after deployment
  • Difference between double-dot “..” and caret / hat symbol “^” in git
  • Everything is working fine except for the add all command which is:

    git add .

    It seems to be working but I don’t get any indication of it working or not. Is there a verbose switch (I think that is what it would be called) that would say what files were tracked after the command is launched?

    I am using Visual Studio 2010 with the standard install of git (Not Git extensions)

  • What is the result of `git push origin`?
  • Is there a way with to prevent “git stash pop” from marking files as modified?
  • How to ignore files starting with numbers in Git?
  • Mirroring repository via fileserver
  • How can I find out what files have changed in the post-checkout hook in git?
  • Can't find branch name in git config file
  • 3 Solutions collect form web for “Does Git Add have a verbose switch”

    git 'command' --verbose


    git 'command' -v.

    Make sure the switch is after the actual git command. Otherwise – it won’
    t work!

    Also useful:

    git 'command' --dry-run 

    Well, like (almost) every console program for unix-like systems, git does not tell you anything if a command succeeds. It prints out something only if there’s something wrong.

    However if you want to be sure of what just happened, just type

    git status

    and see which changes are going to be committed and which not. I suggest you to use this before every commit, just to be sure that you are not forgetting anything.

    Since you seem new to git, here is a link to a free online book that introduces you to git. It’s very useful, it writes about basics as well as well known different workflows:

    You can use git add -i to get an interactive version of git add, although that’s not exactly what you’re after. The simplest thing to do is, after having git added, use git status to see what is staged or not.

    Using git add . isn’t really recommended unless it’s your first commit. It’s usually better to explicitly list the files you want staged, so that you don’t start tracking unwanted files accidentally (temp files and such).

    Git Baby is a git and github fan, let's start git clone.