-
Notifications
You must be signed in to change notification settings - Fork 63.1k
Update duplicating-a-repository.md #16019
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
Conversation
When I pull a`bare` clone of a repository, the name of the folder that gets created is `old-repository.git` whereas the name specified in the docs is just `old-repository`. Updated the same
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. |
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 changesYou 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.
|
@deepansh96 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @deepansh96! Thanks for spotting and making the change. It looks great! I'm going to update from main
and get this merged ✨
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 ⚡ |
Why:
Closes #16018
What's being changed:
When I pull a
--bare
clone of a repository, the name of the folder that gets created isold-repository.git
whereas the name specified in the docs is justold-repository
.Updated the same.
Check off the following:
Writer impact (This section is for GitHub staff members only):