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
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Migrate, Modernize and Build Java Web Apps on Azure: This live workshop will cover methods to enhance Java application development workflow.

Modern Digital Website Security: Prepare to face any form of malicious web activity and enable your sites to optimally serve your customers.

Kubernetes in the Enterprise: The latest expert insights on scaling, serverless, Kubernetes-powered AI, cluster security, FinOps, and more.

E-Commerce Development Essentials: Considering starting or working on an e-commerce business? Learn how to create a backend that scales.

Related

  • Mastering Git
  • Understanding Git
  • The Art of the Bug Fix: Boosting Software Quality Through Effective Git Commits
  • Five Software Development Trends

Trending

  • DZone's Article Submission Guidelines
  • DDD and Microservices
  • How to Submit a Post to DZone
  • What’s New Between Java 17 and Java 21?
  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.

Sudip Bhandari user avatar by
Sudip Bhandari
·
Aug. 07, 18 · Tutorial
Like (2)
Save
Tweet
Share
15.0K Views

Join the DZone community and get the full member experience.

Join For Free

 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, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Mastering Git
  • Understanding Git
  • The Art of the Bug Fix: Boosting Software Quality Through Effective Git Commits
  • Five Software Development Trends

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

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 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: