jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Scannability: Codespaces introductory content (#54688)

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: hubwriter <hubwriter@github.com>
This commit is contained in:
Ben Ahmady
2025-03-11 12:14:17 +00:00
committed by GitHub
parent cba2b19d71
commit 1aea5879b0
31 changed files with 112 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository.md
View File

@@ -55,9 +55,9 @@ When you create a codespace, a number of steps happen to create and connect you
* Step 3: You can connect to the codespace.
* Step 4: Codespace continues with post-creation setup.
For more information on what happens when you create a codespace, see [AUTOTITLE](/codespaces/getting-started/deep-dive).
For more information on what happens when you create a codespace, see [AUTOTITLE](/codespaces/about-codespaces/deep-dive).
For more information on the lifecycle of a codespace, see [AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle).
For more information on the lifecycle of a codespace, see [AUTOTITLE](/codespaces/about-codespaces/understanding-the-codespace-lifecycle).
If you want to use Git hooks for your codespace, then you should set up hooks using the `devcontainer.json` lifecycle scripts, such as `postCreateCommand`. These get executed during step 4, above. For information about the lifecycle scripts, see the [dev containers specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts) on the Development Containers website. Since the dev container for your codespace is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the dev container image will not apply to your codespace. Hooks must instead be installed after the codespace is created.

2
content/codespaces/developing-in-a-codespace/creating-a-codespace-from-a-template.md
View File

@@ -102,5 +102,5 @@ You can publish an unpublished codespace from the "Your codespaces" page on {% d
## Further reading
* [AUTOTITLE](/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)
* [AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle)
* [AUTOTITLE](/codespaces/about-codespaces/understanding-the-codespace-lifecycle)
* [AUTOTITLE](/codespaces/developing-in-a-codespace/using-source-control-in-your-codespace)

2
content/codespaces/developing-in-a-codespace/deleting-a-codespace.md
View File

@@ -141,6 +141,6 @@ You can also use the REST API to delete codespaces for your organization. See [A
## Further reading
* [AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle)
* [AUTOTITLE](/codespaces/about-codespaces/understanding-the-codespace-lifecycle)
* [AUTOTITLE](/codespaces/setting-your-user-preferences/configuring-automatic-deletion-of-your-codespaces)
* [AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)

2
content/codespaces/developing-in-a-codespace/opening-an-existing-codespace.md
View File

@@ -20,7 +20,7 @@ redirect_from:
{% endif %}
You can reopen any of your active or stopped codespaces on {% data variables.product.github %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. See [AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle).
You can reopen any of your active or stopped codespaces on {% data variables.product.github %}, in {% data variables.product.prodname_vscode %}, or by using {% data variables.product.prodname_cli %}. You can't reopen a codespace that has been deleted. See [AUTOTITLE](/codespaces/about-codespaces/understanding-the-codespace-lifecycle).
You can view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can:

2
content/codespaces/developing-in-a-codespace/stopping-and-starting-a-codespace.md
View File

@@ -91,4 +91,4 @@ When you restart a codespace you can choose to open it in {% data variables.prod
## Further reading
* [AUTOTITLE](/codespaces/getting-started/understanding-the-codespace-lifecycle)
* [AUTOTITLE](/codespaces/about-codespaces/understanding-the-codespace-lifecycle)

2
content/codespaces/developing-in-a-codespace/using-github-codespaces-for-pull-requests.md
View File

@@ -15,7 +15,7 @@ redirect_from:
- /codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests
---
Using a codespace to work on a pull request gives you all the benefits of {% data variables.product.prodname_github_codespaces %}. For more information, see [AUTOTITLE](/codespaces/overview#benefits-of-github-codespaces).
Using a codespace to work on a pull request gives you all the benefits of {% data variables.product.prodname_github_codespaces %}. For more information, see [AUTOTITLE](/codespaces/about-codespaces/codespaces-features).
## About pull requests in {% data variables.product.prodname_github_codespaces %}

2
content/codespaces/developing-in-a-codespace/using-github-codespaces-with-github-cli.md
View File

@@ -109,7 +109,7 @@ For more information, see the [{% data variables.product.prodname_dotcom %} CLI
gh codespace stop -c CODESPACE-NAME
```
For more information, see [AUTOTITLE](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace).
For more information, see [AUTOTITLE](/codespaces/about-codespaces/deep-dive#closing-or-stopping-your-codespace).
### Delete a codespace