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 URLs are not case sensitive #34576

Merged
merged 2 commits into from
Sep 16, 2024
Merged

GitHub URLs are not case sensitive #34576

merged 2 commits into from
Sep 16, 2024

Conversation

ewels
Copy link
Contributor

@ewels ewels commented Sep 13, 2024

The example also needed updating. Instead of removing the example completely, I changed it to just show it fixing a spelling mistake (the other topic under the heading).

Why:

Closes: #34573

What's being changed (if available, include any code snippets, screenshots, or gifs):

The docs mention that GitHub git remotes are case sensitive, which is not true.

CleanShot 2024-09-13 at 19 58 28@2x

I removed the part saying that they are case sensitive, and updated the example so that it fixes an actual spelling mistake (cocoareactive instead of ReactiveCocoa):

CleanShot 2024-09-13 at 20 02 00@2x

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

Copy link

welcome bot commented Sep 13, 2024

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 13, 2024
Copy link
Contributor

github-actions bot commented Sep 13, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team repositories Content related to repositories ready to merge This pull request is ready to merge and removed triage Do not begin working on this issue until triaged by the team labels Sep 13, 2024
@nguyenalex836
Copy link
Contributor

@ewels Thank you very much for the fix! Updating the example to fix a spelling mistake is wonderfully clever, thank you ✨

This repo is currently in a code freeze, but we will get this merged as soon as the freeze ends on 9/16! 🍏

@nguyenalex836 nguyenalex836 added this pull request to the merge queue Sep 16, 2024
Merged via the queue into github:main with commit 8b11640 Sep 16, 2024
45 checks passed
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

@ewels ewels deleted the patch-1 branch September 16, 2024 23:08
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 ready to merge This pull request is ready to merge repositories Content related to repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

github repository names are, in fact, (still) not case-sensitive
2 participants