Skip to content

Conversation

@jelle-openai
Copy link
Contributor

In platforms with case-insensitive file systems (such as MacOS by default),
branch names that differ only by casing can collide with each other, because
git stores branches as filenames.

In platforms with case-insensitive file systems (such as MacOS by default),
branch names that differ only by casing can collide with each other, because
git stores branches as filenames.
// file system issues with git branch names.
// prettier-ignore
const chars = "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz-+";
const chars = "0123456789abcdefghijklmnopqrstuvwxyz-";
Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed + too because it can be mildly problematic in some contexts (e.g., URLs) and the code continues to work fine with a shorter alphabet of characters, but happy to put it back if you prefer

@magus
Copy link
Owner

magus commented Jun 25, 2025

Thanks for this fix!

@magus magus merged commit 5ec91f4 into magus:master Jun 25, 2025
@jelle-openai jelle-openai deleted the no-uppercase branch June 25, 2025 22:12
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.

3 participants