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

Remove reference to case-sensitive repositories #32962

Merged
merged 1 commit into from
May 15, 2024

Conversation

jsoref
Copy link
Contributor

@jsoref jsoref commented May 14, 2024

Why:

Closes: #32838

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

Provided an example of a homoglyph repository because those can happen whereas GitHub does not treat owners/repository names case-sensitively.

Before
image

After
image

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.

Provided an example of a homoglyph repository because those can happen whereas GitHub does not treat owners/repository names case-sensitively .
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label May 14, 2024
Copy link
Contributor

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.12 3.11 3.10 3.9
fpt
ghec
ghes@ 3.12 3.11 3.10 3.9

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 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 14, 2024
@nguyenalex836
Copy link
Contributor

@jsoref Thanks so much for opening a PR! I'll get this triaged for review ✨

Copy link
Member

@stevecat stevecat left a comment

Choose a reason for hiding this comment

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

Thank you @jsoref! ✨ I'll get this merged!

@stevecat stevecat added this pull request to the merge queue May 15, 2024
@stevecat stevecat added ready to merge This pull request is ready to merge and removed waiting for review Issue/PR is waiting for a writer's review labels May 15, 2024
@docs-bot docs-bot added this to Triage in Docs open source board May 15, 2024
Merged via the queue into github:main with commit aaa61d6 May 15, 2024
87 checks passed
Docs open source board automation moved this from Triage to Done May 15, 2024
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

@jsoref jsoref deleted the issue-32838 branch May 15, 2024 14:02
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
No open projects
Development

Successfully merging this pull request may close these issues.

github repository names are, in fact, not case-sensitive
3 participants