Skip to content

Conversation

deepansh96
Copy link
Contributor

Why:

Closes #16018

What's being changed:

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.

Check off the following:

  • I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

  • This pull request impacts the contribution experience
    • I have added the 'writer impact' label
    • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

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
@welcome
Copy link

welcome bot commented Mar 3, 2022

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 Mar 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2022

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
content/repositories/creating-and-managing-repositories/duplicating-a-repository.md Modified Original

@ramyaparimi ramyaparimi added content This issue or pull request belongs to the Docs Content team repositories Content related to repositories waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Mar 3, 2022
@ramyaparimi
Copy link
Contributor

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

Copy link
Contributor

@guntrip guntrip left a 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 ✨

@guntrip guntrip enabled auto-merge March 8, 2022 09:37
@guntrip guntrip added the ready to merge This pull request is ready to merge label Mar 8, 2022
@guntrip guntrip merged commit efc4195 into github:main Mar 8, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2022

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

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 waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The instruction in the article "Duplicating a repository" is a little confusing and can be made more clear.
3 participants