Automatically apply "git update-index --chmod=+x" to executable files

Question

I frequently add bash scripts to my Git repository, and the scripts have executable permissions in the Linux filesystem prior to the git add. But after pushing the added files to a remote repository and pulling in another location, the files show up with non-executable permissions. There seem to be two ways to correct the problem:

chmod u+x $script 
git commit -am "fixing the script permissions... again..."

```
git update-index --chmod=+x $script
```

Instead of fixing up the permissions every time, is there a way to have Git simply look at the file permissions on the script during git add, recognize "Hey, this here is an executable file!" and add it to the repository with the executable permissions directly?

Both locations are running linux, so there's no filemode=false issue. I think this is the normal behavior of git--I'm just looking for some way to skip the manual fixup step. — Byron Hawkins
– Byron Hawkins, Commented Jan 11, 2013 at 5:07
Soon with git 2.9/2.10 (Q3 2016), a simple git add --chmod=+x will be enough! See my answer below. — VonC
– VonC, Commented Jul 9, 2016 at 19:15
It would be awesome if this were part of the .gitattributes spec. Something like... *.sh text eol=lf chmod=+x — Anthony Mastrean
– Anthony Mastrean, Commented Mar 1, 2019 at 14:36

Community · Accepted Answer · 2017-05-23 12:18:25Z

git 2.9.X/2.10 (Q3 2016) brings chmod to git add itself!

See commit 4e55ed3 (31 May 2016) by Edward Thomson (ethomson).
Helped-by: Johannes Schindelin (dscho).
^{(Merged by Junio C Hamano -- gitster -- in commit c8b080a, 06 Jul 2016)}

add: add --chmod=+x / --chmod=-x options

The executable bit will not be detected (and therefore will not be set) for paths in a repository with core.filemode set to false, though the users may still wish to add files as executable for compatibility with other users who do have core.filemode functionality.
For example, Windows users adding shell scripts may wish to add them as executable for compatibility with users on non-Windows.

Although this can be done with a plumbing command (git update-index --add --chmod=+x foo), teaching the git-add command allows users to set a file executable with a command that they're already familiar with.

You can see the origin of this new feature in "How to create file execute mode permissions in Git on Windows?" (Feb. 2011)

Michael come lately · Accepted Answer · 2016-06-02 21:29:12Z

24

There are several ways to do that.

Git aliases
Bash aliases
Or even combine bash and git aliases

Git aliases

You can always use bash within your git alias.
- Open your git config:
  
  vim ~/.gitconfig
- Add an aliases section to it (if one does not exist):
```
[alias]
    addscr = !sh -c 'if [[ ${0: -3} == ".sh" ]]; then git update-index --chmod=+x $0; git add $0'
```

Bash aliases

Edit your bash profile file:

vim ~/.bashrc

Add this at the end of the file:

function gitadd(){
    if [[ ${1: -3} == ".sh" ]]
        then git update-index --chmod=+x $1
    fi
    git add $1
 }
 alias gitadd='gitadd'

Combine git and bash aliases

Edit your bash profile file:

vim ~/.bashrc

Add this to the end of the file:

function checkShellFile(){
    return ${1: -3} == ".sh"
}
alias gitadd='checkShellFile ? git addsrcipt "$1" : && git add "$1"'

Edit your git config file:

vim ~/.gitconfig

Add an aliases section to it (if one does not exist):

[alias]
    addscript = !sh -c 'git update-index --chmod=+x $0 && git add $0'

None of the above has been tested

edited Jun 2, 2016 at 21:29

Michael come lately

9,6418 gold badges70 silver badges97 bronze badges

answered Mar 28, 2014 at 10:53

PassTeT

5175 silver badges8 bronze badges

2 Comments

helmesjo Over a year ago

Without googling: Is it possible to do this on a per-repo basis? In case of build agents, I'd like to know beforehand that all checkouts assures correct permissions... :)

Steve Gon Over a year ago

Does this mean that you must use the alias addscr ie git addscr instead of git add from that point on?

Chris McKee · Accepted Answer · 2023-04-14 13:41:36Z

10

Here is a script to automatically apply git update-index --chmod+x to executable files:

for f in $(find . -name '*.sh' -o -regex './s?bin/[^/]+' -o -regex './usr/sbin/[^/]+' -o -regex './usr/lib/[^/]+'); do
     (cd "$(dirname $f)" && git update-index --chmod=+x "$(basename $f)")
done

edited Apr 14, 2023 at 13:41

Chris McKee

4,42711 gold badges52 silver badges83 bronze badges

answered Jul 11, 2014 at 19:13

l0pan

5457 silver badges13 bronze badges

Comments

A. Sallai · Accepted Answer · 2016-12-03 10:37:30Z

A solution without fancy bash scripting:

Set fileMode = true in your .git/config file (or by running git config core.filemode true as others have pointed out)
Change the executable bit on the file's permissions and commit this change. ( chmod u+x $script as you pointed out). You only have to do this once.
Push to the remote

The next time you pull from there, git will set the committed executable bit on the file. I also had similar problems, this solved them.

fileMode = true tells git to track the only thing about permissions it can: the executable bit. This means that changes to the executable bit will be recognized by git as changes in the working tree and those changes will be stored in the repo with your next commit.

Once you committed the desired executable bit you can also reset your fileMode to false so next time git won't bother you with such changes when you don't want to commit them.

eddiemoya · Accepted Answer · 2013-04-01 05:18:56Z

2

I don't think this can be done on the git add command, but you might be able to run a script just right after you run the git commit command, but before the commit is actually created.

Take a look at the pre-commit hook.

http://git-scm.com/book/en/Customizing-Git-Git-Hooks

Basically just create a file in your .git/hooks/ folder called pre-commit. (There should be samples already in your hooks folder, rename them to remove the ".sample" at the end to activate one.)

Theres a gotcha. Make sure your script runs git stash -q first so that your working on the actual staged versions of files.

answered Apr 1, 2013 at 5:18

eddiemoya

7,6771 gold badge26 silver badges35 bronze badges

1 Comment

Eric Roller Over a year ago

github.com/pre-commit/pre-commit-hooks/blob/main/…

dahaze · Accepted Answer · 2024-08-14 07:07:56Z

1

If you are on Windows, using the Tortoise client, just:

Right-click on the file you want to update permission
Select "File Properties"
Select the "Git" tag
Select the checkbox "executable (+x)"
Commit the changes to your repository

answered Aug 14, 2024 at 7:07

dahaze

234 bronze badges

Comments

Smart Coder · Accepted Answer · 2019-09-26 15:56:33Z

0

I just added thru' Tortoise Git folder update. Right click on all files and update the execute permission checkbox to true and commit/push with message. Git Command line add/commit should also work.

answered Sep 26, 2019 at 15:56

Smart Coder

1,77620 silver badges23 bronze badges

Comments

MortenB · Accepted Answer · 2022-08-08 12:54:53Z

0

If you are on windows/powershell, just change path and filter as accordingly:

Get-ChildItem -Path . -Filter '*.py' -Recurse | Select-Object { git -update-index --chmod=+x $_.Name }

answered Aug 8, 2022 at 12:54

MortenB

3,7563 gold badges46 silver badges53 bronze badges

Collectives™ on Stack Overflow

Automatically apply "git update-index --chmod=+x" to executable files

8 Answers 8

`add`: add `--chmod=+x` / `--chmod=-x` options

Comments

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

add: add --chmod=+x / --chmod=-x options

Comments

2 Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related

`add`: add `--chmod=+x` / `--chmod=-x` options