Accessibility: Replace Codespaces screenshots and rewrite alt text (#34864)
Co-authored-by: Laura Coursen <lecoursen@github.com>
This commit is contained in:
hubwriter
@@ -32,7 +32,7 @@ Port forwarding gives you access to TCP ports running within your codespace. For
|
||||
|
||||
|
||||
|
||||
1. Type the port number or address, then press enter.
|
||||
1. Type the port number or address, then press Enter.
|
||||
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ By default, {% data variables.product.prodname_github_codespaces %} forwards por
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Right-click the port you want to update, then hover over **Change Port Protocol**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
|
||||
|
||||
@@ -74,21 +74,23 @@ By default, {% data variables.product.prodname_github_codespaces %} forwards por
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
1. Under the list of ports, click **Add port**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the port number or address, then press enter.
|
||||
1. Type the port number or address, then press Enter.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
|
||||
|
||||
{% data reusables.codespaces.navigate-to-ports-tab %}
|
||||
|
||||
1. Right-click the port that you want to share, click **Port Visibility**, then click **Private to Organization** or **Public**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To the right of the local address for the port, click the copy icon.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Send the copied URL to the person you want to share the port with.
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ You can view all your codespaces on the "Your codespaces" page at [github.com/co
|
||||
1. Click **Open in**.
|
||||
1. Click **Open in APPLICATION**.
|
||||
|
||||
|
||||
|
||||
|
||||
You can open the codespace in:
|
||||
* Your browser
|
||||
|
||||
@@ -57,7 +57,7 @@ You can install and update the JetBrains Gateway from the JetBrains Toolbox appl
|
||||
1. Open the JetBrains Toolbox.
|
||||
1. Find **Gateway** in the list of available tools and click **Install**.
|
||||
|
||||
|
||||
|
||||
|
||||
### {% data variables.product.prodname_cli %}
|
||||
|
||||
@@ -98,10 +98,7 @@ The first time you use JetBrains Gateway for {% data variables.product.prodname_
|
||||
|
||||
|
||||
|
||||
1. In the "Welcome to JetBrains Gateway" dialog box, click **Sign In with {% data variables.product.prodname_dotcom %}**.
|
||||
|
||||
|
||||
|
||||
1. In the "Welcome to JetBrains Gateway" dialog, click **Sign In with {% data variables.product.prodname_dotcom %}**.
|
||||
1. Click the icon beside the one-time code to copy it, then click the login link.
|
||||
|
||||
|
||||
|
||||
@@ -44,9 +44,9 @@ A typical workflow for updating a file using {% data variables.product.prodname_
|
||||
|
||||
## About automatic forking
|
||||
|
||||
You can create a codespace for any repository to which you have write access. If you only have read access to a repository, you can create a codespace for the repository as long as you can fork it.
|
||||
You can create a codespace for any repository to which you have write access. If you only have read access to a repository, you can create a codespace for the repository as long as you can fork it.
|
||||
|
||||
You do not need to fork the repository before you create the codespace. For example, you can create a codespace from the repository to look at the project and make experimental changes, then delete the codespace if you no longer need it.
|
||||
You do not need to fork the repository before you create the codespace. For example, you can create a codespace from the repository to look at the project and make experimental changes, then delete the codespace if you no longer need it.
|
||||
|
||||
If you make a commit from the codespace, {% data variables.product.prodname_github_codespaces %} either creates a fork of the repository under your account and links it to your codespace, or it links your codespace to an existing fork if you already have one for the repository. You can then push your changes to the fork and create a pull request to propose the changes to the upstream repository.
|
||||
|
||||
@@ -79,13 +79,13 @@ For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-re
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.codespaces.source-control %}
|
||||
{% data reusables.codespaces.source-control %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% vscode %}
|
||||
|
||||
{% data reusables.codespaces.source-control %}
|
||||
{% data reusables.codespaces.source-control %}
|
||||
|
||||
{% endvscode %}
|
||||
|
||||
@@ -95,35 +95,35 @@ For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-re
|
||||
|
||||
1. Click the branch name at the right side of the status bar.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the pop-up menu, do one of the following:
|
||||
* To create a new branch based on the current branch, click the name of the current branch, then choose **New Branch**.
|
||||
- **To create a new branch based on the current branch**, click **New Branch**.
|
||||
|
||||
|
||||
|
||||
|
||||
Enter a name for the new branch and click **Create**.
|
||||
|
||||
|
||||
|
||||
|
||||
* To check out an existing branch, start typing the name of the branch you want to check out. Click the branch from the list, then click **Checkout**.
|
||||
- **To check out an existing branch**, start typing the name of the branch you want to check out. Click the branch from the list, then click **Checkout**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
|
||||
**Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
## Committing your changes
|
||||
## Committing your changes
|
||||
|
||||
1. At the right side of the navigation bar, click the check mark.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Commit Changes dialog box, enter a commit message.
|
||||
1. In the Commit Changes dialog, enter a commit message.
|
||||
1. Click **Commit**.
|
||||
|
||||
Alternatively, click the down arrow beside **Commit** and click **Commit and Push**.
|
||||
@@ -136,11 +136,11 @@ You can pull changes from the same branch on the remote repository and apply tho
|
||||
|
||||
1. At the right side of the navigation bar, click the downward pointing arrow.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Update Project dialog box, choose whether you want to merge or rebase the incoming changes.
|
||||
1. In the Update Project dialog, choose whether you want to merge or rebase the incoming changes.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **OK**.
|
||||
|
||||
@@ -150,8 +150,8 @@ You can push changes you've saved and committed. This applies those changes to t
|
||||
|
||||
1. At the right side of the navigation bar, click the upward pointing arrow.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the Push Commits dialog box, click **Push**.
|
||||
1. In the Push Commits dialog, click **Push**.
|
||||
|
||||
{% endjetbrains %}
|
||||
|
||||
Reference in New Issue
Block a user