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

about-git-subtree-merges still uses git URLs for the example remotes #13100

Closed
1 task done
matta opened this issue Dec 17, 2021 · 3 comments · Fixed by #13101
Closed
1 task done

about-git-subtree-merges still uses git URLs for the example remotes #13100

matta opened this issue Dec 17, 2021 · 3 comments · Fixed by #13101
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@matta
Copy link
Contributor

matta commented Dec 17, 2021

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/using-git/about-git-subtree-merges

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

Suggest using https://github.com/octocat/Spoon-Knife.git instead of [email protected]:octocat/Spoon-Knife.git in the example commands.

Additional information

No response

@matta matta added the content This issue or pull request belongs to the Docs Content team label Dec 17, 2021
@welcome
Copy link

welcome bot commented Dec 17, 2021

Thanks for opening this issue. 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 Dec 17, 2021
@ramyaparimi ramyaparimi removed the triage Do not begin working on this issue until triaged by the team label Dec 17, 2021
@arzpgh60

This comment has been minimized.

@arzpgh60

This comment has been minimized.

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@matta @ramyaparimi @arzpgh60 and others