Skip to content

Commit 1ca669b

Browse files
authored
Create codespace.md
1 parent 2fb0764 commit 1ca669b

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

contributing/codespace.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# Working in a codespace
2+
3+
This document describes how to use GitHub Codespaces for working on articles for docs.github.com.
4+
5+
## About GitHub Codespaces
6+
7+
GitHub Codespaces allows you to work in a development environment that's hosted remotely from your machine. You can get started very quickly, with no need to set up the working environment, and without having to download files to your local computer.
8+
9+
GitHub Codespaces is currently only available if you are a member of an organization using GitHub Team or GitHub Enterprise Cloud.
10+
11+
For more information, see "[GitHub Codespaces overview](https://docs.github.com/en/codespaces/overview)."
12+
13+
## Work on documentation in a codespace
14+
15+
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)."
16+
17+
1. Go to the `docs` repository: [https://github.com/github/docs](https://github.com/github/docs).
18+
1. [Fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) to your own organization.
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. Click the **Code** button and click **Create codespace on BRANCHNAME**.
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.
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 `https://docs.github.com/en/`**`codespaces/getting-started/quickstart`** is the markdown file `content/`**`codespaces/getting-started/quickstart`**`.md`.
24+
1. Edit the markdown file as required.
25+
1. Save your changes.
26+
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)."
27+
1. Go to the **Pull requests** tab of the `github/docs` repository and click **New pull request**.
28+
1. Click **compare across forks** and choose the forked repository you created, and your working branch.
29+
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.
30+
1. Click **Create pull request**.
31+
1. Fill out the details for your pull request and click **Create pull request**.
32+
Your pull request will be reviewed by a member of the GitHub documentation team.

0 commit comments

Comments
 (0)