Update screenshots with short alt text (#37829)
This commit is contained in:
Isaac Brown
@@ -21,7 +21,7 @@ You can add personal information about yourself in your bio, like previous place
|
||||
|
||||
{% data reusables.profile.profile-readme %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -45,7 +45,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
|
||||
|
||||
1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
|
||||
|
||||
|
||||
{% data reusables.github-connect.github-connect-tab-user-settings %}
|
||||
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
|
||||
1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**.
|
||||
@@ -55,7 +55,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
|
||||
|
||||
1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
|
||||
|
||||
|
||||
{% data reusables.github-connect.github-connect-tab-user-settings %}
|
||||
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
|
||||
{% data reusables.github-connect.authorize-connection %}
|
||||
|
||||
@@ -37,11 +37,11 @@ Alternatively, you can write your own protection rules for any of the above use
|
||||
1. Optionally, in the **Callback URL** text field under "Identifying and authorizing users," enter the callback URL. For more information, see "[AUTOTITLE](/apps/creating-github-apps/creating-github-apps/about-the-user-authorization-callback-url)."
|
||||
1. Under "Permissions," select **Repository permissions**.
|
||||
1. To the right of "Actions," click the drop down menu and select **Access: Read-only**.
|
||||
|
||||
|
||||
1. To the right of "Deployments," click the drop down menu and select **Access: Read and write**.
|
||||
|
||||
|
||||
1. Under "Subscribe to events," select **Deployment protection rule**.
|
||||
|
||||
|
||||
|
||||
1. Install the custom deployment protection rule in your repositories and enable it for use. For more information, see "[AUTOTITLE](/actions/deployment/protecting-deployments/configuring-custom-deployment-protection-rules)."
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ The following example shows you how {% data variables.product.prodname_actions %
|
||||
```
|
||||
1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
|
||||
|
||||
|
||||
|
||||
|
||||
Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ With {% data variables.product.prodname_actions %}, you can use OpenID Connect (
|
||||
|
||||
The following diagram gives an overview of this solution's architecture:
|
||||
|
||||
|
||||
|
||||
|
||||
It's important that you authenticate not just that the OIDC token came from {% data variables.product.prodname_actions %}, but that it came specifically from your expected workflows, so that other {% data variables.product.prodname_actions %} users aren't able to access services in your private network. You can use OIDC claims to create these conditions. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-trust-conditions-on-cloud-roles-using-oidc-claims)."
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ To configure provisioning for your {% data variables.enterprise.prodname_emu_ent
|
||||
1. Under **Note**, give your token a descriptive name.
|
||||
2. Select the **Expiration** dropdown menu, then click **No expiration**.
|
||||
3. Select the **admin:enterprise** scope.
|
||||
|
||||
|
||||
4. Click **Generate token**.
|
||||
5. To copy the token to your clipboard, click {% octicon "copy" aria-label="Copy token" %}.
|
||||
|
||||
|
||||
@@ -160,7 +160,7 @@ You can view a list of all dormant users {% ifversion ghes or ghae %} who have n
|
||||
|
||||
|
||||
4. Above the list of members, click **Type**, then select the type of members you want to view.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -38,7 +38,7 @@ You can view or download the transaction data to keep track of your subscription
|
||||
- **region:** The name of the region present in billing address.
|
||||
- **postal_code:** The postal code value present in billing address.
|
||||
|
||||
|
||||
|
||||
|
||||
## Accessing {% data variables.product.prodname_marketplace %} transactions
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ To create a {% data variables.product.prodname_marketplace %} listing:
|
||||
{% data reusables.user-settings.edit_marketplace_listing %}
|
||||
5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -110,7 +110,7 @@ If your app only works with specific languages, select up to 10 programming lang
|
||||
|
||||
A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
|
||||
|
||||
|
||||
|
||||
|
||||
As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ You can add multiple public keys to your account on {% data variables.product.pr
|
||||
{% ifversion upload-expired-or-revoked-gpg-key %}
|
||||
To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.gpg.supported-gpg-key-algorithms %}
|
||||
|
||||
@@ -276,7 +276,7 @@ There are other situations where there may be no analysis for the latest commit
|
||||
|
||||
To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_caps %} page, click the **Branch** drop-down and select the relevant branch.
|
||||
|
||||
|
||||
|
||||
|
||||
The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
|
||||
|
||||
|
||||
@@ -94,7 +94,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} automa
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
|
||||
|
||||
You can filter the view to show only alerts where {% data variables.product.prodname_dependabot %} detected at least one call to a vulnerable function using the `has:vulnerable-calls` filter in the search field.
|
||||
|
||||
@@ -196,7 +196,7 @@ If you schedule extensive work to upgrade a dependency, or decide that an alert
|
||||
4. Optionally, at the top of the list of alerts, select all alerts on the page.
|
||||
|
||||
5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ You can use the organization settings page for "Code security and analysis" to e
|
||||
|
||||
{% ifversion secret-scanning-push-protection %}
|
||||
1. Optionally, if you want to enable push protection, click **Enable** to the right of "Push protection." {% data reusables.secret-scanning.push-protection-overview %} For more information, see "[AUTOTITLE](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
1. Before you can enable {% data variables.product.prodname_secret_scanning %}, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
|
||||
|
||||
@@ -38,7 +38,7 @@ The dependency graph shows the dependencies{% ifversion fpt or ghec %} and depen
|
||||
{% ifversion fpt or ghec %}
|
||||
1. Optionally, to view the repositories and packages that depend on your repository, under "Dependency graph", click **Dependents**.
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[AUTOTITLE](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."
|
||||
|
||||
@@ -27,7 +27,7 @@ By default, codespaces are created from an Ubuntu Linux image that includes a se
|
||||
|
||||
You can connect to your codespaces from your browser, from {% data variables.product.prodname_vscode %}, from the JetBrains Gateway application, or by using {% data variables.product.prodname_cli %}. When you connect, you are placed within the Docker container. You do not have access to the outer Linux virtual machine host.
|
||||
|
||||
|
||||
|
||||
|
||||
## Using {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
|
||||
@@ -124,18 +124,18 @@ You can use the default keyboard shortcuts in {% data variables.product.prodname
|
||||
|
||||
If you don't want to use the default keyboard shortcuts in {% data variables.product.prodname_vs %} when using {% data variables.product.prodname_copilot %}, you can rebind the shortcuts in the Keyboard editor using your preferred keyboard shortcuts for each specific command.
|
||||
|
||||
1. In the {% data variables.product.prodname_vs %} toolbar, under **Tools**, click **Options**.
|
||||
1. In the {% data variables.product.prodname_vs %} menu bar, under **Tools**, click **Options**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Options" dialog, under **Environment**, click **Keyboard**.
|
||||
1. Under "Show commands containing:", search for the command you want to rebind.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under "Press shortcut keys," type the shortcut you want to assign to the command, then click **Assign**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.copilot.enabling-or-disabling-vs %}
|
||||
|
||||
@@ -143,8 +143,8 @@ If you don't want to use the default keyboard shortcuts in {% data variables.pro
|
||||
|
||||
If you use ReSharper, {% data variables.product.prodname_copilot %} may work best when you configure ReSharper to use {% data variables.product.prodname_copilot %}'s native IntelliSense. For more information about ReSharper, see the [ReSharper documentation](https://www.jetbrains.com/resharper/documentation/documentation.html)
|
||||
|
||||
1. In the {% data variables.product.prodname_vs %} toolbar, under **Tools**, click **Options**.
|
||||
|
||||
1. In the {% data variables.product.prodname_vs %} menu bar, under **Tools**, click **Options**.
|
||||
|
||||
1. In the "Options" dialog, under **Environment**, click **IntelliSense** and then click **General**.
|
||||
1. Under "General" select **{% data variables.product.prodname_vs %}** and then click **Save**.
|
||||
|
||||
@@ -209,14 +209,14 @@ If you don't want to use the default keyboard shortcuts in {% data variables.pro
|
||||
|
||||
### Rebinding keyboard shortcuts for macOS
|
||||
|
||||
1. Click **Code**, click **Preferences**, then click **Keyboard Shortcuts**.
|
||||
1. In the menu bar, click **Code**, click **Preferences**, then click **Keyboard Shortcuts**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Keyboard Shortcuts" editor, search for the command name of the keyboard shortcut you want to change.
|
||||
1. Next to the command you want to change, click the pencil icon.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the keystrokes you want to use for the command, then press <kbd>Enter</kbd>/<kbd>Return</kbd>.
|
||||
|
||||
@@ -224,12 +224,12 @@ If you don't want to use the default keyboard shortcuts in {% data variables.pro
|
||||
|
||||
1. Click the **File** menu, click **Preferences**, then click **Keyboard Shortcuts**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Keyboard Shortcuts" editor, search for the command name of the keyboard shortcut you want to change.
|
||||
1. Next to the command you want to change, click the pencil icon.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the keystrokes you want to use for the command, then press <kbd>Enter</kbd>/<kbd>Return</kbd>.
|
||||
|
||||
@@ -237,12 +237,12 @@ If you don't want to use the default keyboard shortcuts in {% data variables.pro
|
||||
|
||||
1. Click the **File** menu, click **Preferences**, then click **Keyboard Shortcuts**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Keyboard Shortcuts" editor, search for the command name of the keyboard shortcut you want to change.
|
||||
1. Next to the command you want to change, click the pencil icon.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Type the keystrokes you want to use for the command, then press <kbd>Enter</kbd>/<kbd>Return</kbd>.
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ Depending on the policy settings configured at the enterprise level, an organiza
|
||||
1. If you selected **Start from scratch**, click **Add people** or **Add teams** to add individual users, or entire teams.
|
||||
1. If you selected **Add people**, in the "Enable {% data variables.product.prodname_copilot %} access for selected members of ORGANIZATION" dialog, you can either search for individual members, or you can add members in bulk by uploading a CSV file.
|
||||
|
||||
|
||||
|
||||
|
||||
- To search for members, type the member's username, full name, or email address in the search bar.
|
||||
- To add members in bulk, click **Upload CSV**, and then upload a CSV file including either the username or email address for each member you want to add, separated by a comma.
|
||||
@@ -87,7 +87,7 @@ Removing a user from the organization(s) that had assigned them a {% data variab
|
||||
|
||||
1. Under "Manage access," in the search bar, type the member's username, full name, or email address.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To remove the member from the list of users who have access to {% data variables.product.prodname_copilot %}, click **Remove** on the right side of the page.
|
||||
|
||||
|
||||
@@ -59,15 +59,15 @@ To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you mus
|
||||
1. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**.
|
||||
1. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**.
|
||||
|
||||
|
||||
|
||||
1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
|
||||
1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
|
||||
|
||||
|
||||
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
|
||||
1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
|
||||
@@ -135,7 +135,7 @@ You can enable or disable {% data variables.product.prodname_copilot %} for all
|
||||
|
||||
1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window.
|
||||
|
||||
|
||||
|
||||
1. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing.
|
||||
|
||||
- To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**.
|
||||
@@ -174,16 +174,16 @@ If you use {% data variables.product.prodname_vs %}, you can view and incorporat
|
||||
## Installing the {% data variables.product.prodname_vs %} extension
|
||||
|
||||
To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension.
|
||||
1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**.
|
||||
1. In the Visual Studio menu bar, click **Extensions**, then click **Manage Extensions**.
|
||||
|
||||
|
||||
|
||||
1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**.
|
||||
|
||||
|
||||
|
||||
1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}.
|
||||
1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information.
|
||||
|
||||
|
||||
|
||||
1. Open or create a new project in {% data variables.product.prodname_vs %}.
|
||||
1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**.
|
||||
1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
|
||||
|
||||
@@ -16,7 +16,7 @@ With {% data variables.product.prodname_discussions %}, the community for your p
|
||||
- Upvote discussions and comments to give higher visibility to ideas you find valuable
|
||||
- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows
|
||||
|
||||
|
||||
|
||||
|
||||
You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization.
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ You can choose how to sort the list of discussions.
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
1. To the right of the **Search all discussions** field, select the **Sort by** dropdown menu, and click a time period.
|
||||
|
||||
|
||||
|
||||
|
||||
- Sort by **Latest activity** to display the discussions with the most recent activity at the top of the list.
|
||||
- Sort by **Date created** to display the discussions that were created most recently at the top of the list.
|
||||
|
||||
@@ -116,7 +116,7 @@ You can unpin a globally pinned discussion. This will not delete the discussion,
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-hidden="true" %} **Unpin discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Read the warning, then click **Unpin discussion**.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ You can use discussions insights to help understand the contribution activity, p
|
||||
- **Discussions daily contributors** shows the daily count of unique users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
|
||||
- **Discussions new contributors** shows the daily count of unique new users who have reacted, upvoted, marked an answer, commented, or posted in the selected time period.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -31,6 +31,6 @@ You can use discussions insights to help understand the contribution activity, p
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
1. In the left sidebar, click **Community**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, in the upper-right corner of the page, select the **Period** dropdown menu and click the time period for which you want to view data: **30 days**, **3 months**, or **1 year**.
|
||||
|
||||
@@ -24,7 +24,7 @@ MakeCode Arcade does not support multiplayer-editing for group assignments. Inst
|
||||
|
||||
By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.location.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.location.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -54,7 +54,7 @@ This diagram shows:
|
||||
- A new branch called `feature`
|
||||
- The journey that `feature` takes before it's merged into `main`
|
||||
|
||||
|
||||
|
||||
|
||||
Have you ever saved different versions of a file? Something like:
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ You can customize which items appear in your views using filters for item metada
|
||||
|
||||
To filter a view, click {% octicon "filter" aria-label="Filter by keyword or by field" %} and start typing the fields and values you would like to filter for. As you type, possible values will appear. You can also open the project command palette, by pressing {% data variables.projects.command-palette-shortcut %}, and type "Filter by" to choose from the available filters.
|
||||
|
||||
|
||||
|
||||
|
||||
In board layout, you can click on item data to filter for items with that value. For example, click on an assignee to show only items for that assignee. To remove the filter, click the item data again.
|
||||
|
||||
|
||||
@@ -38,7 +38,7 @@ You can duplicate an existing view and use it as a base to make further changes.
|
||||
|
||||
When you make changes to a view - for example, sorting, reordering, filtering, or grouping the data in a view - a dot is displayed next to the view name to indicate that there are unsaved changes.
|
||||
|
||||
|
||||
|
||||
|
||||
If you don't want to save the changes, you can ignore this indicator. No one else will see your changes.
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@ Now, create a custom field named `Priority` and containing the values: `High`, `
|
||||
|
||||
Specify a priority for all issues in your project.
|
||||
|
||||
|
||||
|
||||
|
||||
## Grouping issues by priority
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ You can only invite an individual user to collaborate on your organization-level
|
||||
|
||||
You can use the **Type** and **Role** drop-down menus to filter the access list.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Edit the role for the collaborator(s).
|
||||
1. Optionally, click **Remove** to remove the collaborator(s).
|
||||
|
||||
@@ -18,7 +18,7 @@ You can customize your organization's Overview page to show a README and pinned
|
||||
|
||||
Members of your organization who are signed into {% data variables.product.prodname_dotcom %}, can select a `member` or `public` view of the README and pinned repositories when they visit your organization's profile page.
|
||||
|
||||
|
||||
|
||||
|
||||
The view defaults to `member` if either a members-only README or members-only pinned repositories are present, and `public` otherwise.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ shortTitle: Compare branches
|
||||
{% endnote %}
|
||||
|
||||
You can view proposed changes in a pull request in the Files changed tab.
|
||||
|
||||
|
||||
|
||||
Rather than viewing the commits themselves, you can view the proposed changes as they'll appear in the files once the pull request is merged. The files appear in alphabetical order within the Files changed tab. Additions to the files appear in green and are prefaced by a `+` sign while content that has been removed appears in red and is prefaced by a `-` sign.
|
||||
|
||||
|
||||
@@ -162,9 +162,9 @@ gh pr create --web
|
||||
{% codespaces %}
|
||||
|
||||
1. Once you've committed changes to your local copy of the repository, click the **Create Pull Request** icon.
|
||||
|
||||
|
||||
1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description.
|
||||
|
||||
|
||||
1. Click **Create**.
|
||||
|
||||
For more information on creating pull requests in {% data variables.product.prodname_github_codespaces %}, see "[AUTOTITLE](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)."
|
||||
|
||||
@@ -36,7 +36,7 @@ A review has three possible statuses:
|
||||
|
||||
You can view all of the reviews a pull request has received in the Conversation timeline, and you can see reviews by repository owners and collaborators in the pull request's merge box.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.search.requested_reviews_search_tip %}
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ You can configure the {% data variables.dependency-review.action_name %} to bett
|
||||
|
||||
1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes.
|
||||
|
||||
|
||||
|
||||
The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -55,19 +55,19 @@ You can use [{% data variables.product.prodname_github_codespaces %}](/codespace
|
||||
1. Open the pull request in a codespace, as described in "[AUTOTITLE](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)."
|
||||
2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace.
|
||||
|
||||
|
||||
|
||||
|
||||
3. To review a specific file, click the **Open File** icon in the Side Bar.
|
||||
|
||||
|
||||
|
||||
|
||||
4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes.
|
||||
|
||||
|
||||
|
||||
|
||||
For more information on reviewing pull requests in {% data variables.product.prodname_github_codespaces %}, see "[AUTOTITLE](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)."
|
||||
|
||||
@@ -83,7 +83,7 @@ If the pull request contains changes to dependencies you can use the dependency
|
||||
|
||||
1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.repositories.return-to-source-diff %}
|
||||
{% endif %}
|
||||
|
||||
@@ -39,7 +39,7 @@ For more information about forks, see "[AUTOTITLE](/pull-requests/collaborating-
|
||||
{% ifversion fpt or ghec %}
|
||||
1. Select **Create a new repository**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ Until you add an image, repository links expand to show basic information about
|
||||
- To add a new image, click **Upload an image...**.
|
||||
- To remove an image, click **Remove image**
|
||||
|
||||
|
||||
|
||||
|
||||
## About transparency
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Referring sites and popular content are ordered by views and unique visitors. Fu
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
|
||||
|
||||
## Accessing the traffic graph
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ Within the blame view, you can view the line-by-line revision history for an ent
|
||||
{% else %}
|
||||
1. In the upper-right corner of the file view, click **Blame** to open the blame view.
|
||||
|
||||
|
||||
|
||||
1. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="View blame prior to this change" %} until you've found the changes you're interested in viewing.
|
||||
|
||||
|
||||
|
||||
@@ -28,6 +28,6 @@ An enterprise owner for {% data variables.product.product_name %} must enable {%
|
||||
|
||||
1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
|
||||
1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
|
||||
|
||||
|
||||
{% data reusables.github-connect.github-connect-tab-user-settings %}
|
||||
{% data reusables.github-connect.connect-dotcom-and-enterprise %}
|
||||
|
||||
@@ -42,7 +42,7 @@ You can only view archived tickets for an enterprise account.
|
||||
|
||||
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
|
||||
|
||||
|
||||
|
||||
1. Under the "My tickets" table, click **View archived tickets**.
|
||||
|
||||
{% endif %}
|
||||
@@ -52,7 +52,7 @@ You can only view archived tickets for an enterprise account.
|
||||
{% data reusables.support.view-open-tickets %}
|
||||
1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
|
||||
2. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
|
||||
|
||||
|
||||
1. To add your comment to the ticket, under the text box, click **Comment**.
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
|
||||
@@ -4,5 +4,5 @@
|
||||
|
||||
{% elsif ghes or ghae %}1. In the top-right corner of {% data variables.product.product_name %}, click your profile photo, then click **Enterprise settings**.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. In the search results, click the name of the user or organization.
|
||||
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
{% data reusables.user-settings.access_org %}
|
||||
1. Under your organization name, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
|
||||
|
||||
|
||||
1. Click **New project**.
|
||||
1. Optionally, in the text box under "Project name", type a name for your new project.
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. Under your repository name, click {% octicon "play" aria-hidden="true" %} **Actions**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. On the pull request, click {% octicon "file-diff" aria-hidden="true" %} **Files changed**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -6,4 +6,4 @@ To create a task list, preface list items with a hyphen and space followed by `[
|
||||
- [ ] Add delight to the experience when all tasks are complete :tada:
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
1. In the upper-right corner of any page, click your profile photo, then click ** Your stars**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -3,6 +3,6 @@
|
||||
|
||||
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
|
||||
|
||||
|
||||
|
||||
1. In the list of tickets, click the subject of the ticket you want to view.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user