Cloning a git repo, and it already has a dirty working directory… Whaaaaa?

by

Which OS are you using? This error is caused by your filesystem not being case sensitive, like the default on Mac OS X.

More Related Contents:

  1. How to revert a merge commit that’s already pushed to remote branch?
  2. Updates were rejected because the remote contains work that you do not have locally
  3. Git push results in “Authentication Failed”
  4. Add line break to ‘git commit -m’ from the command line
  5. Resolving a Git conflict with binary files
  6. Move branch pointer to different commit without checkout
  7. How do I tell git-svn about a remote branch created after I fetched the repo?
  8. GitHub: How to make a fork of public repository private?
  9. ! [rejected] master -> master (fetch first)
  10. rejected master -> master (non-fast-forward)
  11. Checking for a dirty index or untracked files with Git
  12. git move directory to another repository while keeping the history
  13. Local executing hook after a git push?
  14. What does the `..` mean in git branch reference?
  15. How do I rename a repository on GitHub?
  16. Send a pull request on GitHub for only latest commit
  17. git-svn: how do I create a new svn branch via git?
  18. git switch branch without discarding local changes
  19. Automatically apply “git update-index –chmod=+x” to executable files
  20. How to get Git to clone into current directory
  21. How do I create a new Git branch from an old commit? [duplicate]
  22. Why is .gitignore not ignoring my files?
  23. Why call git branch –unset-upstream to fixup?
  24. Differences between git remote update and fetch?
  25. How to create a new (and empty!) “root” branch?
  26. How to keep git from changing file ownership
  27. Git diff says subproject is dirty
  28. git pull keeping local uncommitted changes
  29. How to make ‘git diff’ ignore comments
  30. Git slows down Emacs to Death – How to Fix this?

Leave a Comment