The git commands here seems outdated.

[amhrn]

Why: These git commands did not work for me, so I updated them accordingly.

What's being changed: Only 2 git commands in one file.

Check off the following:

• All of the tests are passing.
• I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
• For content changes, I have reviewed the localization checklist
• For content changes, I have reviewed the Content style guide for GitHub Docs.

[welcome]

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.

[janiceilene]

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

[github-actions]

This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit.

[amhrn]

Hope this minor change gets reviewed soon. Thanks.

[felicitymay]

👋🏻 Hi @mhrn77 I'm on the writing team at GitHub.

Thank you for telling us that you ran into trouble with the steps in this topic and for raising a PR to help other people avoid having the same problem.

Fairly recently we updated our topics to use main as the name for the default branch in line with our decision to use inclusive language.

I've just run through the steps in this topic and successfully added a dummy repository with a default branch of main. It seems as if my computer's set up differently from yours. I know it was a week or so ago that you had the problem, but do you have any information that would help us work out if there are any extra steps that some people need to use?

[amhrn]

Hello @felicitymay,

Thanks for clearing that up. Sorry for the trouble.

[felicitymay]

Hi @mhrn77 - no trouble.

Please continue to let us know where you find problems or room for improvement in the docs.