Any way to not auto stage mode (chmod permission)

[jrgn9]

When I am changing permissions on a file with chmod, it will show up on the "unstaged changes" as

old mode 10644
new mode 10755

There are so many times when I am developing on a script, I need to just try to run it so I change permissions, and then I forgot that I did it, because when selecting which changes to stage, there is not an option to include or drop the mode change.

Are there any way to do this, or do I need to just pay better attention when changing file permissions?

[mark2185]

You can make git itself ignore such changes, but I'm not sure if I'd recommend it.

Basically, this is a "problem" of git, not of lazygit, so I'd suggest to pay better attention to what you're doing.

[jrgn9]

Thanks! I had a feeling it was a git thing. It doesn't happen as frequently anymore, so I guess I just have to just keep on paying attention to it.

[stefanhaller]

If the script is supposed to be run, why don't you check it in with 755 permissions in the first place?

[jrgn9]

I don't have a good answer for that. It's for work, and in the repo all user scripts have 644 by default. And when doing changes I just want to run it quickly to test something, do chmod to run it, do some changes, then sometimes I forget that I changed permissions and push my changes. Not a big deal really, but it happens. So I thought it would be nice to be able to stage the permission like with code blocks to avoid doing minor fuckups like that

[mark2185]

A better "workaround" to that might be to just launch it with the interpreter it's using, e.g. bash <yourscript.sh> and not fiddle with the execution bit.

[jrgn9]

Oh my god @mark2185 that is perfect! I did not know of that, so thank you so much!