DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Gitember: Building a Git Client Beyond Commit, Push, and Pull
  • Closing the Drift Loop: An AI Agent That Drafts Terraform Fixes
  • When a Coding Agent Fixes the Test Instead of the Bug
  • Building a Scope-Constrained AI Agent for Automated CI Failure Repair

Trending

  • Reading GC Logs: Memory Leak or Undersized Heap?
  • Microsoft Foundry Agent Debugging Dashboard with Microsoft Fabric Eventhouse, KQL, Docker and Grafana
  • Agentic Test Creation: From Plain-Language Requirements to End-to-End Test Cases
  • Key ML Classification Metrics You Need to Understand

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Tracking File Permissions in Git

Tracking File Permissions in Git

Take a look at how you can change the permission tracking settings in git so it doesn't create a new file for every single change.

By 
Sudip Bhandari
·
Aug. 07, 18 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
17.4K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

 Although I have been extensively using git for quite some time now, I never happened to come across this situation where you change the permission of the file which is tracked by git. Yes, by default, git is configured to track the changes in file permission mode, too.

Just to experiment with the idea, I created a dummy repo and "touched" an empty file. The initial default permission was 775.

I added the file to staging and changed the permission bit to 777. Git diffing at this point yields an output of following sort:

old mode 100644
new mode 100755


That perfectly reflects the fact that for this particular file, octal permission codes have changed and git has detected that as a change.

You can commit this changed file and it will be tracked by git for the change in permission. You can roll back to the previous commit and the previous permissions will be restored.

However, if you don’t want git to detect file permission changes, which is most likely the case as you probably don’t want to scroll through all the files to find out which ones were actually edited/changed, you can disable the default config by issuing:


git config core.filemode false


Here’s a link to a Stack Overflow question discussing about this issue. To quote one of the comments to understand why git is designed that way:

"This means that git thinks that it can correctly set the executable bit on checked out files, but when it attempts to do so it doesn’t work (or at least not in a way that it can read). When it then reads back the status of those files it looks like the executable bit has been deliberately unset. Setting core.filemode to false tells git to ignore any executable bit changes on the filesystem so it won’t view this as a change. If you do need to stage an executable bit change it does mean that you have to manually do  git update-index --chmod=(+|-)x <path> 

Git

Published at DZone with permission of Sudip Bhandari. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Gitember: Building a Git Client Beyond Commit, Push, and Pull
  • Closing the Drift Loop: An AI Agent That Drafts Terraform Fixes
  • When a Coding Agent Fixes the Test Instead of the Bug
  • Building a Scope-Constrained AI Agent for Automated CI Failure Repair

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook