You need:
git push --force
since you have rewritten the last SHA1 with your --amend, after using git mv
.
It won't break your repo unless you have other collaborators having already pulled from your previous commit as explained in "How do I push amended commit to the remote git repo?".
(in that case, you would need other options for publishing your fixed commit)
On OsX, this answer does suggest (to avoid this issue):
git config --unset-all core.ignorecase
git config --system core.ignorecase false
The OP kyogron reports having found a working solution:
- Create a new branch and checkout this new branch.
- Then delete the
.DS_Store
file in the directory of the corrupted directory and rename it to new name.- Then remove wrong directory in the repository (you can view them with
git ls-files
) and commit this change.- Again remove the
.DS_Store
and now rename the directory to the lower case name you want withgit mv