Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github repository names are, in fact, not case-sensitive #32838

Closed
1 task done
jsoref opened this issue May 7, 2024 · 12 comments · Fixed by #32962
Closed
1 task done

github repository names are, in fact, not case-sensitive #32838

jsoref opened this issue May 7, 2024 · 12 comments · Fixed by #32962
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue repositories Content related to repositories

Comments

@jsoref
Copy link
Contributor

jsoref commented May 7, 2024

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#check-your-spelling

What part(s) of the article would you like to see updated?

Typos happen, and repository names are case-sensitive. If you try to clone `git@{% data variables.command_line.codeblock %}:user/repo.git`, but the repository is really named `User/Repo` you will receive this error.

Typos happen, and repository names are case-sensitive. If you try to clone git@{% data variables.command_line.codeblock %}:user/repo.git, but the repository is really named User/Repo you will receive this error.

This is false.

Additional information

% git clone git@github.com:community/community.git --depth 1 --no-tags
Cloning into 'community'...
remote: Enumerating objects: 52, done.
remote: Counting objects: 100% (52/52), done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 52 (delta 20), reused 21 (delta 7), pack-reused 0
Receiving objects: 100% (52/52), 32.60 KiB | 1.36 MiB/s, done.
Resolving deltas: 100% (20/20), done.
% git clone git@github.com:cOmMuNiTy/CoMmUnItY.git --depth 1 --no-tags
Cloning into 'CoMmUnItY'...
remote: Enumerating objects: 52, done.
remote: Counting objects: 100% (52/52), done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 52 (delta 20), reused 21 (delta 7), pack-reused 0
Receiving objects: 100% (52/52), 32.61 KiB | 1.42 MiB/s, done.
Resolving deltas: 100% (20/20), done.
@jsoref jsoref added the content This issue or pull request belongs to the Docs Content team label May 7, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label May 7, 2024
@nguyenalex836 nguyenalex836 added waiting for review Issue/PR is waiting for a writer's review repositories Content related to repositories and removed triage Do not begin working on this issue until triaged by the team labels May 7, 2024
@nguyenalex836
Copy link
Contributor

@jsoref Thank you for opening this issue! I'll get this triaged for review ✨

@P3k0pl

This comment was marked as spam.

@P3k0pl

This comment was marked as spam.

@P3k0pl

This comment was marked as spam.

@Tinneke40

This comment was marked as spam.

@Tinneke40

This comment was marked as spam.

@yasser01147310161

This comment was marked as spam.

@stevecat
Copy link
Member

Hey @jsoref, thanks for opening this! ✨ It looks like this was the case at some point many years ago but the docs were never updated when this changed.

I think we can just remove that entire line from the article. You (or anyone else!) is very welcome to open a PR to make this change!

@stevecat stevecat added help wanted Anyone is welcome to open a pull request to fix this issue good first issue Good for newcomers and removed waiting for review Issue/PR is waiting for a writer's review labels May 14, 2024
@docs-bot docs-bot added this to Help wanted in Docs open source board May 14, 2024
@jsoref
Copy link
Contributor Author

jsoref commented May 14, 2024

I'm inclined to change the example to a homograph (0O/Il1) as the point about copying instead of retyping still stands.

If you have a suggestion for the homograph, we can take it.

@stevecat
Copy link
Member

I think the existing content, once the first line is removed, serves this section well:

To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "Cloning a repository."

To update the remote on an existing repository, see "Managing remote repositories".

A homograph would be two words that sound the same but are spelt differently (close/close). I understand what you mean about characters that can look alike and be confusing (I, l, and 1 as you suggested) but I think the existing suggestion to copy/paste covers this. We're usually wary of adding more content than is necessary. If I've misunderstood, feel free to open your PR with the example and we can review it! ✨

@jsoref
Copy link
Contributor Author

jsoref commented May 14, 2024

Sorry. I meant homoglyph.

Docs open source board automation moved this from Help wanted to Done May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers help wanted Anyone is welcome to open a pull request to fix this issue repositories Content related to repositories
Development

Successfully merging a pull request may close this issue.

8 participants
@jsoref @stevecat @nguyenalex836 @yasser01147310161 @P3k0pl @Tinneke40 and others