Git-Training-Hub/tech-thursday-demo
26
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

#2 - Git Case Sensitivity and File Renaming Assignment #2

New Issue
Open
opened 2025-09-02 10:13:59 +00:00 by jebin.jebamony · 13 comments
jebin.jebamony commented 2025-09-02 10:13:59 +00:00
Member
Copy Link

Assignment: Git Case Sensitivity Issue

You are working in a Git repository that already contains a file named readme.md.
You decide to rename the file to README.md (changing only the case of the filename).

After renaming, you notice that Git does not show any change when running git status.

Task

  1. Reproduce this situation in your local Git repository.
  2. Investigate why Git is not tracking this case-only rename.
  3. Provide the correct steps to make Git recognize and commit the rename.
  4. Explain the underlying reason why this happens (hint: think about how Git interacts with different operating systems and filesystems).

Deliverables

  • Comment your explanation and observations in this git issue.
# Assignment: Git Case Sensitivity Issue You are working in a Git repository that already contains a file named **`readme.md`**. You decide to rename the file to **`README.md`** (changing only the case of the filename). After renaming, you notice that Git does **not** show any change when running `git status`. --- ## Task 1. Reproduce this situation in your local Git repository. 2. Investigate **why** Git is not tracking this case-only rename. 3. Provide the correct steps to make Git recognize and commit the rename. 4. Explain the underlying reason why this happens (hint: think about how Git interacts with different operating systems and filesystems). --- ## Deliverables - Comment your explanation and observations in this git issue.
ajin.vijayakumar was assigned by jebin.jebamony 2025-09-02 10:21:46 +00:00
ajishini.chandrasekar was assigned by jebin.jebamony 2025-09-02 10:21:46 +00:00
Arjun.Gopi was assigned by jebin.jebamony 2025-09-02 10:21:46 +00:00
asaph.johnwesley was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
ashish.livingston was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
gokul.subramonian was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
jaya.lekshmi was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
leyo.whiteson.rabertsingh was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
Magdel was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
muralikrishnan.rajamuni was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
nikhil.samuel was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
rahul.bruce was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
renejit.vedamoni was assigned by jebin.jebamony 2025-09-02 10:21:47 +00:00
solomon.antony was assigned by jebin.jebamony 2025-09-02 10:21:48 +00:00
vipinraj.vijayakamaladas was assigned by jebin.jebamony 2025-09-02 10:21:48 +00:00
renejit.vedamoni commented 2025-09-04 06:19:24 +00:00
Member
Copy Link

Git is case-sensitive but relies on filesystem system calls (e.g., stat). Case-sensitive filesystems (Linux) treat case-only renames as distinct, updating Git’s index. Case-insensitive filesystems (macOS, Windows) report no change, as core.ignorecase is true, aligning Git with the filesystem’s behavior.

Git is case-sensitive but relies on filesystem system calls (e.g., stat). Case-sensitive filesystems (Linux) treat case-only renames as distinct, updating Git’s index. Case-insensitive filesystems (macOS, Windows) report no change, as core.ignorecase is true, aligning Git with the filesystem’s behavior.
gokul.subramonian commented 2025-09-04 06:25:14 +00:00
Member
Copy Link

why Git is not tracking this case-only rename?

    Windows/macOS filesystems are case-insensitive they treat both names as the same file.So when you rename only by case, the OS reports no change.

Provide the correct steps to make Git recognize and commit the rename:
force Rename command : git mv -f readme.md Readme.md

Explain the underlying reason why this happens (hint: think about how Git interacts with different operating systems and filesystems).

 1. Git was designed for Linux, where filesystems are case-sensitive.
 2. Windows/macOS filesystems are case-insensitive they treat both names as the same file.So when you rename only by case, the OS reports no change.
why Git is not tracking this case-only rename? Windows/macOS filesystems are case-insensitive they treat both names as the same file.So when you rename only by case, the OS reports no change. Provide the correct steps to make Git recognize and commit the rename: force Rename command : git mv -f readme.md Readme.md Explain the underlying reason why this happens (hint: think about how Git interacts with different operating systems and filesystems). 1. Git was designed for Linux, where filesystems are case-sensitive. 2. Windows/macOS filesystems are case-insensitive they treat both names as the same file.So when you rename only by case, the OS reports no change.
solomon.antony commented 2025-09-04 06:40:03 +00:00
Member
Copy Link

On Windows and macOS, filesystems are case-insensitive.
They treat File.txt and file.txt as the same file (even though they preserve the casing you type).
So if you rename only by changing the case, the OS reports “no change.”

Provide the correct steps to make Git recognize and commit the rename:
force Rename command : git mv -f readme.md Readme.md

On Windows and macOS, filesystems are case-insensitive. They treat File.txt and file.txt as the same file (even though they preserve the casing you type). So if you rename only by changing the case, the OS reports “no change.” Provide the correct steps to make Git recognize and commit the rename: force Rename command : git mv -f readme.md Readme.md
leyo.whiteson.rabertsingh commented 2025-09-04 06:56:33 +00:00
Member
Copy Link

windows use case insensitive systems so both the file looks same and git checks the file and thinks nothing changed.If we want to rename we need to force git to recognize. Renaming to temporary name and then to the desired name
Git itself is case sensitive on Linux so it sees the difference but on windows or macOS it is case insensitive so it hides the difference . That's why we need two step rename method.

windows use case insensitive systems so both the file looks same and git checks the file and thinks nothing changed.If we want to rename we need to force git to recognize. Renaming to temporary name and then to the desired name Git itself is case sensitive on Linux so it sees the difference but on windows or macOS it is case insensitive so it hides the difference . That's why we need two step rename method.
ashish.livingston commented 2025-09-04 07:46:08 +00:00
Member
Copy Link

Git is case-sensitive, but Windows/macOS filesystems are case-insensitive. The OS treats readme.md and README.md as the same file, so Git does not detect the rename.

Solution: Use Git’s force move to make the rename explicit.

git mv -f readme.md README.md git commit -m "Rename readme.md to README.md" git push origin main

Git is case-sensitive, but Windows/macOS filesystems are case-insensitive. The OS treats readme.md and README.md as the same file, so Git does not detect the rename. Solution: Use Git’s force move to make the rename explicit. git mv -f readme.md README.md git commit -m "Rename readme.md to README.md" git push origin main
muralikrishnan.rajamuni commented 2025-09-04 09:05:48 +00:00
Member
Copy Link

On case-insensitive filesystems (like Windows or macOS by default), Git will not show any rename because the OS treats readme.md and README.md as the same file.

Git is case-sensitive, but many operating systems’ filesystems (Windows, macOS HFS+) are case-insensitive but case-preserving.

To make Git recognize a case-only rename on case-insensitive filesystems, do it in two steps:
git mv readme.md temp.md
git commit -m "Temporary rename"

git mv temp.md README.md
git commit -m "Rename readme.md to README.md"

Git itself is case-sensitive because it was designed for Linux filesystems (ext4, case-sensitive).
Windows and macOS filesystems are usually case-insensitive.

On case-insensitive filesystems (like Windows or macOS by default), Git will not show any rename because the OS treats readme.md and README.md as the same file. Git is case-sensitive, but many operating systems’ filesystems (Windows, macOS HFS+) are case-insensitive but case-preserving. To make Git recognize a case-only rename on case-insensitive filesystems, do it in two steps: git mv readme.md temp.md git commit -m "Temporary rename" git mv temp.md README.md git commit -m "Rename readme.md to README.md" Git itself is case-sensitive because it was designed for Linux filesystems (ext4, case-sensitive). Windows and macOS filesystems are usually case-insensitive.
ajin.vijayakumar commented 2025-09-04 09:09:11 +00:00
Member
Copy Link

  • Issue: Renamed readme.md, README.md. Git showed no change (git status).

  • Reason: Git is case-sensitive, Windows is not, Git ignores case-only rename.

  • Fix:

git mv -f readme.md README.md

git commit -m "Rename file case"
  • On Windows, force rename is needed because of case-insensitive filesystem.
* **Issue:** Renamed readme.md, README.md. Git showed no change (`git status`). * **Reason:** Git is case-sensitive, Windows is not, Git ignores case-only rename. * **Fix:** ``` git mv -f readme.md README.md ``` ``` git commit -m "Rename file case" ``` * On Windows, force rename is needed because of case-insensitive filesystem.
ajishini.chandrasekar commented 2025-09-04 14:11:27 +00:00
Member
Copy Link
  • Created readme.md in a repo and renamed it to README.md
  • Git didn’t show changes because windows system is case-insensitive
  • Fixed it using:
    git mv -f readme.md README.md
    git commit -m "Rename readme.md to README.md"
  • Reason: Git is case-sensitive, but case-insensitive filesystems treat both names as the same
- Created readme.md in a repo and renamed it to README.md - Git didn’t show changes because windows system is case-insensitive - Fixed it using: `git mv -f readme.md README.md` `git commit -m "Rename readme.md to README.md"` - Reason: Git is case-sensitive, but case-insensitive filesystems treat both names as the same
rahul.bruce commented 2025-09-05 04:05:19 +00:00
Member
Copy Link

This problem happens because Git can tell the difference between uppercase and lowercase letters, but your computer’s system (like Windows or Mac) usually cannot. So when you rename readme.md to README.md, Git does not see it as a change. To fix this, you can force Git to notice by running git mv -f readme.md README.md and then committing it. On Linux, this issue usually doesn’t happen because the system can tell the difference between file name cases.

This problem happens because Git can tell the difference between uppercase and lowercase letters, but your computer’s system (like Windows or Mac) usually cannot. So when you rename readme.md to README.md, Git does not see it as a change. To fix this, you can force Git to notice by running git mv -f readme.md README.md and then committing it. On Linux, this issue usually doesn’t happen because the system can tell the difference between file name cases.
jaya.lekshmi commented 2025-09-06 06:22:41 +00:00
Member
Copy Link
  • Created readme.md in a repo and renamed it to README.md
  • Git didn’t show changes because windows system is case-insensitive
  • Fixed it using:
    git mv -f readme.md README.md
    git commit -m "Rename readme.md to README.md"
  • Reason: Git is case-sensitive, but case-insensitive filesystems treat both names as the same
- Created readme.md in a repo and renamed it to README.md - Git didn’t show changes because windows system is case-insensitive - Fixed it using: `git mv -f readme.md README.md` `git commit -m "Rename readme.md to README.md"` - Reason: Git is case-sensitive, but case-insensitive filesystems treat both names as the same
Magdel commented 2025-09-06 06:40:21 +00:00
Member
Copy Link

Recreate the problem:

  • initialise repository
  • Create file readme.md by using git add
  • commit the file
  • use mv to rename the file to README.md
  • check git status
    RESULT: no changes detected in file name

This problem isn't inherent from git [is case senstive], rather from the underlying filing system of the OS the local repository runs on. The filing system doesn't detect any changes in file names because it's not case insensitive. So readme.md and README.md are treated as the same file unless the user explicitly forces or manipulates Git into noticing the changes in file name. The OS itself cannot be made to see the changes, however a command can be made for Git to override OS behaviour of case insensitivity. This can be acheived using two options:

Option 1: Two-Step Process
Renaming the file into a temporary file name, before naming it to the intented file name. For example, readme.md can be renamed to newfile.md for git to see a full file name change. This is because case changes are left to the filing system to recognise. newfile.md can then be changed to README.md for the changes to be recongised, because of a full name change again.

git mv readme.md newfile.md
git mv newfile.md README.md

Option 2: Force Command
Another command is to force Git to track the changes regardless of what the OS filing system thinks using the force -f flag.

git mv -f readme.md README.md
**Recreate the problem:** - initialise repository - Create file `readme.md` by using git add - commit the file - use mv to rename the file to `README.md` - check git status _RESULT: no changes detected in file name_ This problem isn't inherent from git [is case senstive], rather from the underlying filing system of the OS the local repository runs on. The filing system doesn't detect any changes in file names because it's not case insensitive. So `readme.md` and `README.md` are treated as the same file unless the user explicitly forces or manipulates Git into noticing the changes in file name. _The OS itself cannot be made to see the changes, however a command can be made for Git to override OS behaviour of case insensitivity._ This can be acheived using two options: **Option 1: Two-Step Process** Renaming the file into a temporary file name, before naming it to the intented file name. For example, `readme.md` can be renamed to `newfile.md` for git to see a full file name change. This is because case changes are left to the filing system to recognise. `newfile.md` can then be changed to `README.md` for the changes to be recongised, because of a full name change again. ``` git mv readme.md newfile.md git mv newfile.md README.md ``` **Option 2: Force Command** Another command is to force Git to track the changes regardless of what the OS filing system thinks using the force `-f` flag. ``` git mv -f readme.md README.md ```
nikhil.samuel commented 2025-09-11 04:11:55 +00:00
Member
Copy Link

If a Linux user renames readme.md → README.md, pushes to GitHub, and a Windows user pulls:

Windows sees them as the same file.

This can cause conflicts, overwritten files, or invisible renames.

  • On Linux, readme.md and README.md are two different files.
    -On Windows/macOS (case-insensitive FS), they are treated as the same file.
If a Linux user renames readme.md → README.md, pushes to GitHub, and a Windows user pulls: Windows sees them as the same file. This can cause conflicts, overwritten files, or invisible renames. - On Linux, readme.md and README.md are two different files. -On Windows/macOS (case-insensitive FS), they are treated as the same file.
Arjun.Gopi commented 2025-09-11 06:03:59 +00:00
Member
Copy Link

On case-insensitive file systems (like Windows or macOS by default), renaming readme.md → README.md does not appear as a change to Git.
That’s because the OS treats both names as the same file.
solution1:
git config core.ignorecase false

On case-insensitive file systems (like Windows or macOS by default), renaming readme.md → README.md does not appear as a change to Git. That’s because the OS treats both names as the same file. solution1: git config core.ignorecase false
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ajin.vijayakumar ajishini.chandrasekar anikuttan.test.admin.account anikuttan.vijayakumar aravinth.nagarajan Arjun.Gopi asaph.johnwesley ashish.livingston dhanush.kannan gokul.subramonian januson.john jaya.lekshmi jebin.jebamony jeeva jemima.emmanuel jerisha.yesuthangaraja leyo.whiteson.rabertsingh Magdel muralikrishnan.rajamuni nikhil.samuel rahul.bruce renejit.vedamoni rishika.kaliappapillai solomon.antony subitha.ps vipinraj.vijayakamaladas
No Assignees ajin.vijayakumar ajishini.chandrasekar Arjun.Gopi asaph.johnwesley ashish.livingston gokul.subramonian jaya.lekshmi leyo.whiteson.rabertsingh Magdel muralikrishnan.rajamuni nikhil.samuel rahul.bruce renejit.vedamoni solomon.antony vipinraj.vijayakamaladas
14 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Git-Training-Hub/tech-thursday-demo#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?