Should be pointed out for the record, especially for new Git users (and considering OP's comment above: "Theres a couple project files in my trunk i ignore.", or another comment: "How do I use the backed-up repo to restore the working tree?"), that:
- one thing is the Git "repo", and
- another thing is your actual project dir (or workspace etc.), which is the Git repo + the "work tree" (i.e. all other files you may still need, like precious login credentials, not in the repo!)
In many actual backup (and especially migration) cases the actual focus is not just on the repo itself, but on all the "project stuff", which is both the Git repo, and all the other work files, either checked in to the Git repo or not (being ".gitignored").
For these cases (where the whole project workspace is to be replicated), the only correct procedure seems to be copying the whole project dir tree (including, but not limited to the Git repo).
(The accepted answer said that, but didn't explain why it would actually be the preferred way: this can be a life-saver when restoring the backup a year later only to see the checked-in master branch and nothing else, which cannot be built, tested, deployed, or even opened in an IDE, without all the "ignored" work-tree files.)