How can I check whether a git repository has any commits in it?

I am writing a custom git command that should only run in a completely new repository with no commits (see this question). How can I perform a simple check within my script to see if an existing repo has zero commits?

Essentially, what goes in the blank below?

  • How do I remove a repository from SmartGit?
  • How to push a branch back to a private github repo
  • Downloading a directory inside a git repo
  • How to change the behavior of git status showing modified files which are eventually not committed?
  • How to keep a second git remote repository for selected commits (states)
  • “git svn rebase” without changing the current branch
  • if ___________ ; then
        echo "Git repo already has commits. Aborting.
    else
        echo "Git repo has no commits. Doing whatever my script does."
    fi
    

  • force update the current branch - how?
  • Which is official GUI of Git for windows?
  • Why admin can't add himself to project member in gitlab?
  • Proper workflow using git and github
  • How can I automatically synchronize a Github repository to a SourceForge repository
  • How to accept the 'Did you mean?' terminal/git suggestion
  • 2 Solutions collect form web for “How can I check whether a git repository has any commits in it?”

    Summary:

    • A commit is checked out: test git rev-parse HEAD &> /dev/null
    • A ref pointing to a commit exists: test git rev-list -n 1 --all &> /dev/null
    • Objects exist in the repo: test output of git fsck, git count-objects, or the examine the contents of .git/objects

    And now for the discussion!

    If you want to know whether a commit is checked out, you can use git rev-parse HEAD. There will be output, so you probably want to redirect to /dev/null and just use the exit code. For all practical purposes, this will be good enough – doing normal things, it’s pretty much impossible to end up without HEAD pointing at anything. But it is possible, for example by deleting files in the .git directory. Depending on your script, this might be important – if you’re about to blow away the .git directory, you want to be paranoid indeed.

    If you want to see whether there are any refs at all with commits on them, you can use git rev-list -n 1 --all. Again, there will be output (the SHA1 of the first commit encountered), so redirect to /dev/null and check the exit code.

    Finally, if you want to check if there are any commits – even if they aren’t on any refs (you have to try really hard to get into this state) I’d probably just check for the presence of objects with git fsck or git count-objects – or failing that, list .git/objects and check for anything besides info and pack (commands tend to fail if there is no file .git/HEAD). And yes, you could actually have a repo with blobs and trees but no commits, but you’d have to try even harder to get there. These are the absolute safest methods, if your script is scary.

    You want to use git log

    If you are using cygwin or are on a linux machine gitk is a useful program to have as well.

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