Skip to content

Improve branch renaming to handle case-only changes#21323

Merged
tidy-dev merged 2 commits intodevelopmentfrom
case-sensitive-renames
Dec 3, 2025
Merged

Improve branch renaming to handle case-only changes#21323
tidy-dev merged 2 commits intodevelopmentfrom
case-sensitive-renames

Conversation

@niik
Copy link
Member

@niik niik commented Nov 28, 2025

Closes #21320

Description

Enhanced the renameBranch function to retry with force (-M) when a case-only branch rename fails due to case-insensitive filesystems. Added getBranchNames utility to verify branch existence and prevent unsafe renames.

Screenshots

Release notes

Notes:

niik added 2 commits November 28, 2025 12:01
Enhanced the renameBranch function to retry with force (-M) when a case-only branch rename fails due to case-insensitive filesystems. Added getBranchNames utility to verify branch existence and prevent unsafe renames.
Copy link
Contributor

@tidy-dev tidy-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense

@tidy-dev tidy-dev merged commit 29bb579 into development Dec 3, 2025
8 checks passed
@tidy-dev tidy-dev deleted the case-sensitive-renames branch December 3, 2025 14:38
Copy link

@SEUB66 SEUB66 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks bro :) i aPreciate. Thing being hard today i'm old school

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve branch renaming UX on Windows (Case-only changes require double rename)

3 participants