Skip to content

Commit 95d2d58

Browse files
authored
Update codespace.md
1 parent d92a0f2 commit 95d2d58

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

contributing/codespace.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ For more information, see "[GitHub Codespaces overview](https://docs.github.com/
1515
The steps described below assume you have GitHub Codespaces set up to edit files using Visual Studio Code for Web. The steps are very similar if you have configured a different editor. For more information, see "[Setting your default editor for GitHub Codespaces](https://docs.github.com/en/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)."
1616

1717
1. Go to the `docs` repository: [https://github.com/github/docs](https://github.com/github/docs).
18-
1. If you're an open source contributor, [fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your own organization.
18+
1. If you're an open source contributor: [fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your own organization.
1919
1. [Create a branch to work on](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository).
2020
1. On the main page of the new `docs` repository, click the **Code** button and click **Create codespace on BRANCHNAME**.<br>
2121
The "Setting up your codespace" page is displayed. After a short time the browser-based version of Visual Studio Code is displayed.
@@ -26,8 +26,9 @@ The steps described below assume you have GitHub Codespaces set up to edit files
2626
1. Commit and push your changes, either using the Source Control pane, or using Git commands from the Terminal. For more information, see "[About Git](https://docs.github.com/en/get-started/using-git/about-git)."
2727
1. Go to the **Pull requests** tab of the `github/docs` repository: https://github.com/github/docs/pulls
2828
1. Click **New pull request**.
29-
1. Click **compare across forks** and choose the forked repository you created, and your working branch.
30-
1. Check that the changes displayed include all of the changes you made in the codespace. If they do not, it indicates there are changes you have not pushed from the codespace to GitHub.
31-
1. Click **Create pull request**.
32-
1. Fill out the details for your pull request and click **Create pull request**.<br>
29+
1. If you're an open source contributor: click **compare across forks** and choose the forked repository you created, and your working branch.<br>
30+
Otherwise: change the "compare" branch to your working branch.
31+
3. Check that the changes displayed include all of the changes you made in the codespace. If they do not, it indicates there are changes you have not pushed from the codespace to GitHub.
32+
4. Click **Create pull request**.
33+
5. Fill out the details for your pull request and click **Create pull request**.<br>
3334
Your pull request will be reviewed by a member of the GitHub documentation team.

0 commit comments

Comments
 (0)