开发者

Git file permissions on Windows

开发者 https://www.devze.com 2023-03-15 13:46 出处:网络
I\'ve read through a few questions regarding file permissions in Git and I\'m still a bit confused. I\'ve got a repo on GitHub forked from another. Post merge, they should be identical. However:

I've read through a few questions regarding file permissions in Git and I'm still a bit confused. I've got a repo on GitHub forked from another. Post merge, they should be identical. However:

$ git diff --summary origin/epsilon m开发者_如何转开发aster/epsilon
 mode change 100644 => 100755 ants/dist/sample_bots/csharp/compile.sh
 mode change 100644 => 100755 ants/dist/starter_bots/coffeescript/MyBot.coffee
 mode change 100644 => 100755 ants/dist/starter_bots/coffeescript/ants.coffee
 mode change 100644 => 100755 ants/util/block_test.sh
 mode change 100644 => 100755 manager/mass_skill_update.py
 mode change 100644 => 100755 worker/jailguard.py
 mode change 100644 => 100755 worker/release_stale_jails.py
 mode change 100644 => 100755 worker/start_worker.sh

I've tried changing file permissions, but it does not alter the diff results.


I found the solution of how to change permissions (also) on Windows here: http://blog.lesc.se/2011/11/how-to-change-file-premissions-in-git.html

For example following command adds user execute permission to an arbitrary file:

git update-index --chmod=+x <file>


From another question here on stackoverflow: How do I make Git ignore file mode (chmod) changes?

First see what core.filemode is set to -

git config core.filemode

Try setting it to false:

git config core.filemode false

From git-config(1):

   core.fileMode
       If false, the executable bit differences between the index and the
       working copy are ignored; useful on broken filesystems like FAT.
       See git-update-index(1). True by default.


Handy one-liner for Git Bash:

find . -name '*.sh' | xargs git update-index --chmod=+x

It will mark all .sh file as executable. After that, you just have to git commit.


If you use Cygwin git (or Linux git, too, I assume), there's a good chance your core.filemode setting has been set at the project level in $projdir/.git/config . I found that I had to do the following to get my Cygwin git and my Windows git to coexist nicely on a Windows filesystem without nonexistent filemode changes showing up all the time:

  • delete the line setting core.filemode in $projdir/.git/config
  • in Windows git, run "git config --global core.filemode false"

This allows my Cygwin git to continue to see filemode changes, which are usually relevant, while instructing the Windows git to ignore the filemode changes it sees, which are usually false positives.


First check file permissions using below command.

git ls-files --stage

Then change permissions. Here "x" represents execute permissions.

git update-index --chmod=+x 'scriptname.ext'

Now re-verify the permissions.

git ls-files --stage

NB: If you are running Windows and deploying on Linux, be sure the repository contains code with Unix-like line endings. To bulk-convert files, you could try dos2unix.exe, or work in Git Bash.


I fixed it by changing the file permissions in Ubuntu, commit, push and all OK. Seems it just wouldn't work with msysgit on Windows/NTFS.


In my case, I accidentally shifted the shebang line so that

#! /bin/sh

became

   #! /bin/sh

This fails the git-bash permission check. After removing the leading whitespaces, the script becomes executable again.

0

精彩评论

暂无评论...
验证码 换一张
取 消