File name case changes not reflected after commit and push


### Description

When renaming a file with only a change in letter casing (e.g., `district` → `District`), Git does not properly update the filename on the remote repository. Instead, the file remains with the old lowercase name (`district`) even after committing and pushing the change.

Steps to Reproduce

  1. Create a file named district.
  2. Commit and push to the remote repository.
  3. Rename the file locally to District (changing only the case).
  4. Commit and push again.

Actual Behavior

The remote repository still shows the file as district (lowercase), even though locally it appears as District (uppercase).

Expected Behavior

The remote repository should update the file name to reflect the correct casing (District).

Possible Cause

On case-insensitive file systems (e.g., Windows, macOS by default), Git does not detect case-only renames by default. This causes the filename change to not propagate correctly to the remote repository.

Edited by 🤖 GitLab Bot 🤖