You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributing/codespace.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ The steps described below assume you have GitHub Codespaces set up to edit files
17
17
1. Go to the `docs` repository: [https://github.com/github/docs](https://github.com/github/docs).
18
18
1.[Fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your own organization.
19
19
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).
20
-
1. On the main page of the new `docs` repository, click the **Code** button and click **Create codespace on BRANCHNAME**.
20
+
1. On the main page of the new `docs` repository, click the **Code** button and click **Create codespace on BRANCHNAME**.<br>
21
21
The "Setting up your codespace" page is displayed. After a short time the browser-based version of Visual Studio Code is displayed.
22
-
1. Use the Explorer to navigate to the markdown file you want to edit. This will be located below the `content` directory.
22
+
1. Use the Explorer to navigate to the markdown file you want to edit. This will be located below the `content` directory. <br>
23
23
In most cases, the path to the file, below the `content` directory, matches the path in URL, minus the `.md` file name extension. For example, the source for the article <code>https<span></span>://docs.github.com/en/**codespaces/getting-started/quickstart**</code> is the markdown file <code>content/**codespaces/getting-started/quickstart**.md</code>.
24
24
1. Edit the markdown file as required.
25
25
1. Save your changes.
@@ -29,5 +29,5 @@ The steps described below assume you have GitHub Codespaces set up to edit files
29
29
1. Click **compare across forks** and choose the forked repository you created, and your working branch.
30
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
31
1. Click **Create pull request**.
32
-
1. Fill out the details for your pull request and click **Create pull request**.
32
+
1. Fill out the details for your pull request and click **Create pull request**.<br>
33
33
Your pull request will be reviewed by a member of the GitHub documentation team.
0 commit comments