fatal: could not open '.git/COMMIT_EDITMSG': Permission denied
- Recovering from accidental git pull on octopress branches
- Octopress - source branch suddenly is pushing to master
- Update of blog site via cron does not work
- Git commit ERROR: Repository invalid
- Rake w/Git says 'fatal: Will not add file alias' but I can do it manually?
- Octopress blog deploying error 'rake aborted! No such file or directory - git remote -v'
It all worked well until the commit part, where I get error:
fatal: could not open ‘.git/COMMIT_EDITMSG’: Permission denied
I am the owner of my github.io page, of course, and I never had this issue before. Why is this happening, and more importantly how do I resolve it?
8 Solutions collect form web for “fatal: could not open '.git/COMMIT_EDITMSG': Permission denied”
This is not an error message from the remote Git repository, this is a problem with your local files. You probably used git (or rake) as another user (such as root) in this same directory, and it created files which you now can’t overwrite.
Simply use chown to change the ownership of the files to your current user, for instance:
chown --recursive $(id -u) .
I solved it by deleting
.git/COMMIT_EDITMSG. Weird, I know.
If you are working on the bloody Microsoft Windows the error might be due to the fact that you are “watching” the hidden files in the file explorer..that´s it!
another solution for Windows users:
if you are using YandexDisk – and your .git folder under syncronisation –
YandexDisk set hidden and readonly attributes after syncronisations.
So, switch off YandexDisk and make .git folder and all subfolders and files NOT invisible and not readonly
chmod 664 the file
.git/COMMIT_EDITMSG gives it group write permissions.
In my situation the file was owned by another user who was part of my development group. Giving it group write permissions solved it.
.git directory should be in the root of your repository.
Command (assuming you are in the .git directory):
chmod 664 COMMIT_EDITMSG
If you’re using TortoiseGit, you may have a Commit dialog already open
This tends not to be a permissions issue.
This situation may occur when you are prompted to record a commit message when merging (for example) and you don’t save and quit the text editor but you simply quit.
Git seems to assume there is still someone editting a commit message and refuses to overwrite the existing file as it would cause unexpected behaviour and loss of another commit message.
Simply run on your command line : chmod 777 -Rf /var/www/html/project-name/.git