update lists to commonmark (#37249)
This commit is contained in:
Rachael Sewell
@@ -47,14 +47,14 @@ When you unsubscribe from notifications in your inbox, they will automatically d
|
||||
1. From the notifications inbox, select the notifications you want to unsubscribe to.
|
||||
2. Click **Unsubscribe.**
|
||||
|
||||
|
||||
|
||||
|
||||
## Unsubscribing from notifications on the subscriptions page
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories, select the "Manage notifications" dropdown menu and click **Subscriptions**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select the notifications you want to unsubscribe from. In the top right, click **Unsubscribe**.
|
||||
|
||||
@@ -65,7 +65,7 @@ When you unwatch a repository, you unsubscribe from future updates from that rep
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories, select the "Manage notifications" dropdown menu and click **Watched repositories**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
|
||||
|
||||
|
||||
@@ -46,11 +46,11 @@ Many people forget about repositories that they've chosen to watch in the past.
|
||||
|
||||
{% data reusables.notifications.access_notifications %}
|
||||
1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
|
||||
|
||||
|
||||
|
||||
2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -64,7 +64,7 @@ Many people forget about repositories that they've chosen to watch in the past.
|
||||
## Reviewing repositories that you're watching
|
||||
|
||||
1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
|
||||
|
||||
|
||||
2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -69,7 +69,7 @@ You can add up to 15 of your own custom filters.
|
||||
|
||||
3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)."
|
||||
|
||||
|
||||
|
||||
|
||||
4. Click **Create**.
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ To save a single notification to review later, to the right of the notification,
|
||||
|
||||
Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day.
|
||||
|
||||
|
||||
|
||||
|
||||
## Investigating a notification
|
||||
|
||||
@@ -38,7 +38,7 @@ You can choose how you want to receive future notifications for a specific issue
|
||||
|
||||
1. In the right column of the issue or pull request, next to "Notifications", click **Customize**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. In the dialog box, select **Custom**, then choose when you'd like to receive a notification update for this thread. For example, you can choose to receive an update when the pull request has been merged, closed, or reopened. You will be subscribed again if you participate in the thread, your username is @mentioned, or a team you're a member of is @mentioned.
|
||||
|
||||
|
||||
@@ -27,4 +27,4 @@ shortTitle: Show an overview
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. Above your contributions graph, select the **Contribution settings** dropdown menu, then click **Activity overview**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ Since an email address can only be associated with a single {% data variables.pr
|
||||
|
||||
1. In the email, click **Unlink this email**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To finish unlinking your email, on {% data variables.product.prodname_dotcom_the_website %}, click **Unlink**.
|
||||
1. Optionally, to create a new account and link your newly unlinked email, click **Create a new account**.
|
||||
|
||||
@@ -59,7 +59,7 @@ You can download the log files from your workflow run. You can also download a w
|
||||
{% data reusables.repositories.navigate-to-job %}
|
||||
1. In the upper right corner of the log, select the {% octicon "gear" aria-label="Show options" %} dropdown menu, then click **Download log archive**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion re-run-jobs %}
|
||||
|
||||
|
||||
@@ -41,4 +41,4 @@ Before enabling license synchronization on {% data variables.location.product_lo
|
||||
{% data reusables.enterprise-accounts.github-connect-tab %}
|
||||
1. To the right of "License sync", click **Enable**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -38,10 +38,10 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
|
||||
1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**.
|
||||
1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page.
|
||||
|
||||
|
||||
|
||||
1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository.
|
||||
|
||||
|
||||
|
||||
1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository)."
|
||||
1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
|
||||
1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
@@ -62,7 +62,7 @@ For example, you can configure {% data variables.location.product_location %} to
|
||||
{% data reusables.enterprise-accounts.hooks-tab %}
|
||||
5. Next to the webhook you'd like to edit, click **Edit**.
|
||||
|
||||
|
||||
|
||||
6. Update the webhook's settings.
|
||||
7. Click **Update webhook**.
|
||||
|
||||
@@ -82,7 +82,7 @@ For example, you can configure {% data variables.location.product_location %} to
|
||||
{% data reusables.enterprise-accounts.hooks-tab %}
|
||||
5. In the list of webhooks, click the URL of the webhook for which you'd like to see deliveries.
|
||||
|
||||
|
||||
|
||||
6. Under "Recent deliveries", click a delivery GUID to view details.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -27,5 +27,5 @@ You can also enforce your default setting on all current organization members in
|
||||
{% data reusables.enterprise-accounts.options-tab %}
|
||||
1. Under "Default organization membership visibility", select the drop-down menu, and click **Private** or **Public**.
|
||||
1. Optionally, to prevent members from changing their membership visibility from the default, select **Enforce for all enterprise members**.
|
||||
{% ifversion ghes %}
|
||||
{% ifversion ghes %}
|
||||
1. If you'd like to enforce your new visibility setting on all existing members, use the `ghe-org-membership-update` command-line utility. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-org-membership-update)."{% endif %}
|
||||
|
||||
@@ -75,7 +75,7 @@ If the administrator you want to remove is a member of any organizations owned b
|
||||
{% data reusables.enterprise-accounts.administrators-tab %}
|
||||
{%- ifversion ghec or ghes > 3.6 %}
|
||||
1. Next to the username of the person you'd like to remove, select the {% octicon "kebab-horizontal" aria-label="Administrator settings" %} dropdown menu, then click **Convert to member**{% ifversion ghec %} or **Remove from enterprise**{% endif %}.
|
||||
|
||||
|
||||
1. Read the confirmation, then click **Yes, convert USERNAME to member**{% ifversion ghec %} or **Yes, remove USERNAME**{% endif %}.
|
||||
{%- else %}
|
||||
1. Next to the username of the person you'd like to remove, select the {% octicon "gear" aria-label="Administrator settings" %} dropdown menu, then click **Remove owner**.
|
||||
|
||||
@@ -41,7 +41,7 @@ To remove yourself from your organization:
|
||||
{% ifversion 2fa-reconfiguration-inline-update %}
|
||||
1. Hover over **Enabled**, then click **Disable**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. If necessary, enter your password or perform 2FA once more to disable 2FA for your {% data variables.product.prodname_dotcom %} account.
|
||||
{% else %}
|
||||
|
||||
@@ -24,7 +24,7 @@ Each license for {% data variables.product.prodname_GH_advanced_security %} spec
|
||||
2. Under "Committers", click **Manage committers**.
|
||||
3. Under "Total committers", click the plus or minus buttons to add or remove committers.
|
||||
|
||||
|
||||
|
||||
1. Click **Update committers**.
|
||||
|
||||
## Canceling your {% data variables.product.prodname_GH_advanced_security %} subscription
|
||||
|
||||
@@ -114,12 +114,12 @@ You can download the {% data variables.product.prodname_advanced_security %} lic
|
||||
{%- ifversion ghec %}
|
||||
1. Under "{% data variables.product.prodname_GH_advanced_security %}," click the **Manage** dropdown and then click **Download report**.
|
||||
|
||||
|
||||
|
||||
|
||||
{%- elsif ghes > 3.8 %}
|
||||
1. Under "{% data variables.product.prodname_GH_advanced_security %}," click {% octicon "download" aria-hidden="true" %} **CSV report** in the header of the "Committers" table.
|
||||
|
||||
|
||||
|
||||
|
||||
{%- else %}
|
||||
1. Under "{% data variables.product.prodname_GH_advanced_security %}," {% octicon "download" aria-label="The download icon" %} in the header of the "Committers" table.
|
||||
|
||||
@@ -67,7 +67,7 @@ Enterprise owners and billing managers can manage the spending limit for {% data
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. On the "Billing" page, click the **Spending limit** tab.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.dotcom_billing.monthly-spending-limit-actions-packages %}
|
||||
{% data reusables.dotcom_billing.update-spending-limit %}
|
||||
|
||||
@@ -39,7 +39,7 @@ If you downgrade your personal account from {% data variables.product.prodname_p
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.billing_plans %}
|
||||
1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**.
|
||||
|
||||
|
||||
5. Read the information about the features your personal account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**.
|
||||
|
||||
If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, to avoid the risk of a domain takeover. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)."
|
||||
@@ -61,7 +61,7 @@ Downgrading from {% data variables.product.prodname_ghe_cloud %} disables any SA
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want.
|
||||
|
||||
|
||||
{% data reusables.dotcom_billing.confirm_cancel_org_plan %}
|
||||
|
||||
## Downgrading an organization's subscription with legacy per-repository pricing
|
||||
|
||||
@@ -36,8 +36,7 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.billing_plans_payment %}
|
||||
1. At the bottom of the page, next to "Additional information," click **Add information**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.dotcom_billing.extra_info_receipt %}
|
||||
|
||||
@@ -56,6 +55,6 @@ Your receipts include your {% data variables.product.prodname_dotcom %} subscrip
|
||||
|
||||
1. Under "Payment information", next to "Additional information click **Add information**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.dotcom_billing.extra_info_receipt %}
|
||||
@@ -35,7 +35,7 @@ Your organization's billing email is where {% data variables.product.product_nam
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "Billing management", under "Email recipients", find the email address you want to change and click **Edit**.
|
||||
|
||||
|
||||
2. Type a valid email address, then click **Update**.
|
||||
|
||||
## Managing additional recipients for your organization's billing email
|
||||
@@ -48,7 +48,7 @@ If you have users that want to receive billing reports, you can add their email
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "Billing management", to the right of "Email recipients", click **Add**.
|
||||
|
||||
|
||||
1. Type the email address of the recipient, then click **Add**.
|
||||
|
||||
### Changing the primary recipient for billing notifications for your organization
|
||||
@@ -58,14 +58,14 @@ One address must always be designated as the primary recipient. The address with
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "Billing management", under "Email recipients", find the email address you want to set as the primary recipient.
|
||||
1. To the right of the email address, select **Edit**, then click **Mark as primary**.
|
||||
|
||||
|
||||
|
||||
### Removing a recipient from billing notifications for your organization
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "Email recipients", find the email address you want to remove.
|
||||
1. To the right of the email address, select "Edit", then click **Remove**.
|
||||
|
||||
|
||||
1. Review the confirmation prompt, then click **Remove**.
|
||||
|
||||
{% ifversion ghec %}
|
||||
@@ -80,7 +80,7 @@ Only enterprise members with the owner or billing manager role can access or cha
|
||||
{% data reusables.enterprise-accounts.billing-tab %}
|
||||
1. Click **Billing emails**.
|
||||
1. Under "Email recipients", to the right of the billing email address, click **Edit**.
|
||||
|
||||
|
||||
1. Type a valid email address, then click **Update**.
|
||||
|
||||
## Managing additional recipients for your enterprise's billing email
|
||||
|
||||
@@ -37,7 +37,7 @@ The code scanning alerts page for each repository includes a tools banner with a
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-code-scanning-alerts %}
|
||||
1. Click **Tool status** in the tools banner.
|
||||
|
||||
|
||||
|
||||
## Using the {% data variables.code-scanning.tool_status_page %}
|
||||
|
||||
|
||||
@@ -73,11 +73,11 @@ Try default setup if you don't need to run extra queries, change the scan schedu
|
||||
{% data reusables.user-settings.security-analysis %}
|
||||
1. In the "{% data variables.product.prodname_code_scanning_caps %}" section, select **Set up** {% octicon "triangle-down" aria-hidden="true" %}, then click **Default**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, in the "Query suites" section of the "{% data variables.product.prodname_codeql %} default configuration" modal dialog, select the **Default** {% octicon "triangle-down" aria-hidden="true" %} dropdown menu, then click the {% data variables.product.prodname_codeql %} query suite you would like to use.
|
||||
|
||||
|
||||
|
||||
|
||||
If you choose the **Extended** query suite, your {% data variables.product.prodname_code_scanning %} configuration will run lower severity and precision queries in addition to the queries included in the **Default** query suite.
|
||||
|
||||
@@ -226,7 +226,7 @@ After configuring {% data variables.product.prodname_code_scanning %} for your r
|
||||
|
||||
1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Review the logging output from the actions in this workflow as they run.
|
||||
|
||||
|
||||
@@ -116,7 +116,7 @@ You can search the list of alerts. This is useful if there is a large number of
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-code-scanning-alerts %}
|
||||
1. To the right of the **Filters** drop-down menus, type the keywords to search for in the free text search box.
|
||||
|
||||
|
||||
1. Press <kbd>return</kbd>. The alert listing will contain the open {% data variables.product.prodname_code_scanning %} alerts matching your search criteria.
|
||||
|
||||
{% endif %}
|
||||
@@ -191,10 +191,10 @@ To dismiss {% ifversion delete-code-scanning-alerts %}or delete{% endif %} alert
|
||||
1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
|
||||
{%- ifversion comment-dismissed-code-scanning-alert %}
|
||||
1. Review the alert, then click **Dismiss alert** and choose, or type, a reason for closing the alert.
|
||||
|
||||
|
||||
{%- else %}
|
||||
1. Review the alert, then click **Dismiss** and choose a reason for closing the alert.
|
||||
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.code-scanning.choose-alert-dismissal-reason %}
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@ After configuring {% data variables.product.prodname_code_scanning %} for your r
|
||||
|
||||
1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Review the logging output from the actions in this workflow as they run.
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@ You can filter to see which alerts have been auto-dismissed, and you can reopen
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
1. To filter to see all closed alerts, click **{% octicon "check" aria-hidden="true" %} Closed**. Alternatively, use the `is:closed` filter query in the search bar.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To see all auto-dismissed alerts, select **Closed as**, then in the dropdown menu, click **Auto-dismissed**.
|
||||
|
||||
|
||||
@@ -153,7 +153,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version.
|
||||
{% elsif ghae %}
|
||||
|
||||
@@ -38,7 +38,7 @@ Collaborators have write permissions to the security advisory. For more informat
|
||||
4. In the "Security Advisories" list, click the security advisory you'd like to add a collaborator to.
|
||||
5. On the right side of the page, under "Collaborators", type the name of the user or team you'd like to add to the security advisory.
|
||||
6. Click **{% octicon "plus" aria-label="Add Collaborator" %}** to add the selected user or team as a collaborator.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ Anyone with write permissions to a security advisory can create a pull request f
|
||||
1. In the "Security Advisories" list, click the name of the security advisory you'd like to create a pull request in.
|
||||
1. Scroll to the bottom of the advisory form. Then, under "Collaborate on a patch", click **Compare & pull request** to create a pull request for the associated branch.
|
||||
|
||||
|
||||
|
||||
The "Open a pull request" includes a header showing the branches that will be compared in a three-dot Git diff comparison when the pull request is created. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons)."
|
||||
{% data reusables.repositories.create-pull-request %}
|
||||
|
||||
@@ -90,7 +90,7 @@ Additionally, there can be no merge conflicts, and {% data variables.product.pro
|
||||
1. In the "Security Advisories" list, click the name of the security advisory with changes that you'd like to merge.
|
||||
1. Scroll to the bottom of the advisory form. Then, under "This advisory is ready to be merged", click **Merge pull request(s)** to merge all open pull requests in the temporary private fork.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -29,8 +29,7 @@ The instructions in this article refer to enablement at repository level. For in
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-code-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-security-researcher %}
|
||||
|
||||
|
||||
@@ -29,16 +29,14 @@ The instructions below refer to enablement at organization level. For informatio
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable all** or **Disable all**, to enable or disable the feature for all the public repositories within the organization, respectively.
|
||||
|
||||
|
||||
|
||||
|
||||
## Enabling or disabling private vulnerability reporting for new public repositories added to the organization
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of the feature, click **Automatically enable for new public repositories**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To the right of "Private vulnerability reporting", click **Enable all** or **Disable all**, to enable or disable the feature for all new public repositories that will be added to the organization, respectively.
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
|
||||
4. In the "Security Advisories" list, click the name of the security advisory you'd like to publish.
|
||||
5. Scroll to the bottom of the advisory form and click **Publish advisory**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -97,7 +97,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
|
||||
4. In the "Security Advisories" list, click the name of the security advisory you'd like to request a CVE identification number for.
|
||||
6. Scroll to the bottom of the advisory form and click **Request CVE**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ People with admin permissions to a security advisory can remove collaborators fr
|
||||
5. On the right side of the page, under "Collaborators", find the name of the user or team you'd like to remove from the security advisory.
|
||||
6. Next to the collaborator you want to remove, click **Remove**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ The following steps describe how to export your changes to a branch or fork. For
|
||||
1. Click the ellipsis (**...**) to the right of the codespace you want to export from.
|
||||
1. Select **{% octicon "git-branch" aria-hidden="true" %} Export changes to a branch** or **{% octicon "git-branch" aria-hidden="true" %} Export changes to a fork**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. From the popover or dialog box, select **Create branch** or **Create fork**.
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ If a comment is off-topic, outdated, or resolved, you may want to hide a comment
|
||||
1. Navigate to the comment you'd like to hide.
|
||||
2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Hide**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Using the "Choose a reason" dropdown menu, choose a reason to hide the comment. Then select **Hide comment**.
|
||||
{% ifversion fpt or ghec %}
|
||||
@@ -93,7 +93,7 @@ Deleting a comment creates a timeline event that is visible to anyone with read
|
||||
|
||||
1. Navigate to the comment you'd like to delete.
|
||||
2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
|
||||
|
||||
|
||||
3. Optionally, write a comment noting that you deleted a comment and why.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
@@ -30,7 +30,7 @@ When you delete sensitive information from the comment's edit history, the perso
|
||||
1. Navigate to the comment where you would like to delete sensitive information from the edit history.
|
||||
{% data reusables.repositories.edited-comment-list %}
|
||||
3. In the top right of the edit history window, click **Options**. Then click **Delete revision from history** to delete the diff that shows the content being added.
|
||||
|
||||
|
||||
4. To confirm deletion, click **OK**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -31,7 +31,7 @@ You can create a default code of conduct for your organization or personal accou
|
||||
{% data reusables.files.add-file %}
|
||||
3. In the file name field, type *CODE_OF_CONDUCT.md*.
|
||||
4. Select **Choose a code of conduct template**.
|
||||
|
||||
|
||||
5. On the left side of the page, select a code of conduct to preview and add to your project.
|
||||
6. On the right side of the page, complete the fields to populate the selected code of conduct with the appropriate information.
|
||||
7. Click **Review and submit**.
|
||||
|
||||
@@ -48,7 +48,7 @@ You cannot create a default license file. License files must be added to individ
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
1. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
|
||||
|
||||
|
||||
1. In the "Repository name" field, type **.github**.
|
||||
1. Optionally, in the "Description" field, type a description.
|
||||
2. Make sure the repository status is set to **Public**. A repository for default files cannot be private.
|
||||
|
||||
@@ -22,7 +22,7 @@ You can apply the `good first issue` label to issues in your public repository s
|
||||
{% data reusables.repositories.select-items-in-issue-or-pr-list %}
|
||||
1. Above the list of issues, select the **Label** dropdown menu.
|
||||
|
||||
|
||||
|
||||
1. In the "Search filters" field, start typing `good first issue`. Click the label's name to associate it with the selected items.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -304,7 +304,7 @@ After you have revoked authorization, if you want to continue using {% data vari
|
||||
|
||||
1. In the bottom left corner of {% data variables.product.prodname_vscode %}, click the **Accounts** icon, hover over your username, and click **Sign in with {% data variables.product.prodname_dotcom %} to use {% data variables.product.prodname_copilot %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Continue**.
|
||||
1. In the "Open {% data variables.product.prodname_vscode %}?" pop-up, click **Open {% data variables.product.prodname_vscode %}**.
|
||||
|
||||
@@ -17,9 +17,9 @@ shortTitle: Add a repository
|
||||
{% mac %}
|
||||
|
||||
1. In the menu bar, select **File**, then click **Add Local Repository**.
|
||||
|
||||
|
||||
2. In the "Add Local Repository" window, click **Choose...**, then use the Finder window to navigate to the local repository you want to add.
|
||||
|
||||
|
||||
3. When you have chosen the local repository, in the "Add Local Repository" window, click **Add Repository**.
|
||||
|
||||
{% endmac %}
|
||||
@@ -27,9 +27,9 @@ shortTitle: Add a repository
|
||||
{% windows %}
|
||||
|
||||
1. In the menu bar, select **File**, then click **Add local repository**.
|
||||
|
||||
|
||||
2. In the "Add local repository" window, click **Choose...**, then use Windows Explorer to navigate to the local repository you want to add.
|
||||
|
||||
|
||||
4. Click **Add repository**.
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -19,7 +19,7 @@ shortTitle: Commit & review changes
|
||||
|
||||
1. [Create a new branch](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches-in-github-desktop), or select an existing branch by clicking {% octicon "git-branch" aria-hidden="true" %} **Current Branch** on the toolbar and selecting the branch from the list.
|
||||
|
||||
|
||||
|
||||
{% data reusables.desktop.make-changes %}
|
||||
|
||||
## Choosing how to display diffs
|
||||
@@ -107,7 +107,7 @@ Once you're satisfied with the changes you've chosen to include in your commit,
|
||||
|
||||
1. Optionally, to attribute a commit to another author, click the add co-authors icon and type the username(s) you want to include.
|
||||
|
||||
|
||||
|
||||
{% data reusables.desktop.commit-button %}
|
||||
4. If the branch you're trying to commit to is protected, Desktop will warn you.
|
||||
- To move your changes, click **switch branches**.
|
||||
|
||||
@@ -50,7 +50,7 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
|
||||
{% data reusables.desktop.history-tab %}
|
||||
2. Right-click on the commit you would like to create a new branch from and select **Create Branch from Commit**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.desktop.name-branch %}
|
||||
{% data reusables.desktop.confirm-new-branch-button %}
|
||||
@@ -60,9 +60,9 @@ You can always create a branch in {% data variables.product.prodname_desktop %}
|
||||
If you create a branch on {% data variables.product.product_name %}, you'll need to publish the branch to make it available for collaboration on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to publish.
|
||||
|
||||
|
||||
2. Click **Publish branch**.
|
||||
|
||||
|
||||
|
||||
## Switching between branches
|
||||
|
||||
@@ -74,7 +74,7 @@ You can view and make commits to any of your repository's branches. If you have
|
||||
{% endtip %}
|
||||
|
||||
1. In the repository bar, click {% octicon "git-branch" aria-hidden="true" %} **Current Branch**, then click the branch that you want to switch to.
|
||||
|
||||
|
||||
1. If you have saved, uncommitted changes, in the "Switch Branch" window, select **Leave my changes on CURRENT-BRANCH** or **Bring my changes to NEW-BRANCH**, then click **Switch Branch**.
|
||||
|
||||
## Deleting a branch
|
||||
|
||||
@@ -19,7 +19,7 @@ You can continue to amend a commit until you push it to the remote repository. A
|
||||
{% data reusables.desktop.history-tab %}
|
||||
1. Right-click on the most recent commit and select **Amend commit**.
|
||||
|
||||
|
||||
|
||||
1. In the "Amend Will Require Force Push" dialog window, click **Begin Amend**.
|
||||
1. In the "Changes" tab, use the **Summary** field to modify the commit message. Optionally, you can modify or add information about the commit in the **Description** field.
|
||||
1. Select any uncommitted changes that you would like to add to the commit. For more information about selecting changes, see "[AUTOTITLE](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit)."
|
||||
|
||||
@@ -19,12 +19,12 @@ You can also use cherry-picking when collaborating with a team. Some projects in
|
||||
{% data reusables.desktop.current-branch-menu %}
|
||||
2. In the list of branches, click the branch that has the commit that you want to cherry-pick.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.desktop.history-tab %}
|
||||
4. Drag the commit that you want to cherry-pick from the "History" tab to the {% octicon "git-branch" aria-hidden="true" %} **Current Branch** dropdown menu, then drop the commit on the branch that you want to copy the commit to.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
- [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation
|
||||
|
||||
@@ -17,12 +17,12 @@ Reordering allows you to alter your commit history to provide a more meaningful
|
||||
{% data reusables.desktop.current-branch-menu %}
|
||||
2. In the list of branches, click the branch with the commits that you want to reorder.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.desktop.history-tab %}
|
||||
4. Drag the commit that you want to reorder and drop it between two adjoining commits.
|
||||
|
||||
|
||||
|
||||
|
||||
While the application reorders the commits, a **Reorder in process** dialog indicates the progress of the change.
|
||||
|
||||
|
||||
@@ -66,7 +66,7 @@ Before you create a pull request, you'll need to push changes to a branch on {%
|
||||
|
||||
Alternatively, to go straight to {% data variables.product.prodname_dotcom %} to create your pull request, select the dropdown icon and click **Create Pull Request**.
|
||||
1. Confirm that the branch in the **base:** dropdown menu is the branch where you want to merge your changes.
|
||||
|
||||
|
||||
|
||||
{% data variables.product.prodname_desktop %} will advise you whether the current branch can be automatically merged into the base branch.
|
||||
|
||||
|
||||
@@ -19,11 +19,11 @@ versions:
|
||||
{% data reusables.desktop.choose-pr-from-list %}
|
||||
4. Click on the pull request number, to the right of the pull request branch name.
|
||||
|
||||
|
||||
|
||||
5. To re-run failed checks, click **{% octicon "sync" aria-hidden="true" %} Re-run** and select **Re-run Failed Checks**.
|
||||
|
||||
|
||||
|
||||
6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check.
|
||||
|
||||
|
||||
|
||||
7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run.
|
||||
|
||||
@@ -79,7 +79,7 @@ shortTitle: Configure default editor
|
||||
|
||||
{% data reusables.desktop.mac-select-desktop-menu %}
|
||||
3. In the Preferences window, select **Integrations**.
|
||||
|
||||
|
||||
4. Under "External Editor", use the dropdown menu to select the editor you want to set as your default.
|
||||
5. Click **Save**.
|
||||
|
||||
@@ -89,7 +89,7 @@ shortTitle: Configure default editor
|
||||
|
||||
{% data reusables.desktop.windows-choose-options %}
|
||||
3. In the Options window, select **Integrations**.
|
||||
|
||||
|
||||
4. Under "External Editor", use the dropdown menu to select the editor you want to set as your default.
|
||||
5. Click **Save**.
|
||||
|
||||
|
||||
@@ -88,7 +88,7 @@ For some errors, {% data variables.product.prodname_desktop %} will prompt you w
|
||||
|
||||
1. In the menu bar, select **Help**, then click **Show Logs in Finder**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select the log file from the date when you encountered the authentication error.
|
||||
|
||||
@@ -98,7 +98,7 @@ For some errors, {% data variables.product.prodname_desktop %} will prompt you w
|
||||
|
||||
1. Use the **Help** drop-down menu and click **Show Logs in Explorer**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select the log file from the date when you encountered the authentication error.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: Uninstalling
|
||||
|
||||
1. Open Control Panel. For more information, see [Where is Control Panel?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) in Windows Help.
|
||||
2. Under "Programs", click **Uninstall a program**.
|
||||
|
||||
|
||||
3. Right-click the entry named **{% data variables.product.prodname_desktop %}**, then click **Uninstall**.
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -80,14 +80,14 @@ When you create a new repository, it only exists on your computer and you are th
|
||||
Now that you've created and published your repository, you're ready to make changes to your project and start crafting your first commit to your repository.
|
||||
|
||||
1. To launch your external editor from within {% data variables.product.prodname_desktop %}, in the "{% data variables.product.prodname_desktop %}" menu bar, select **Repository**, then click **Open in EDITOR**. For more information, see "[AUTOTITLE](/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor-in-github-desktop)."
|
||||
|
||||
|
||||
|
||||
2. Make some changes to the _README.md_ file that you previously created. You can add information that describes your project, like what it does and why it is useful. When you are satisfied with your changes, save them in your text editor.
|
||||
3. In {% data variables.product.prodname_desktop %}, navigate to the **Changes** view. In the file list, you should see your _README.md_. The checkbox to the left of the _README.md_ file indicates that the changes you've made to the file will be part of the commit you make. In the future, you might make changes to multiple files but only want to commit the changes you've made to some of the files. If you click the checkbox next to a file, that file will not be included in the commit.
|
||||
|
||||
|
||||
|
||||
4. At the bottom of the **Changes** list, enter a commit message. To the right of your profile picture, type a short description of the commit. Since we're changing the _README.md_ file, "Add information about purpose of project" would be a good commit summary. Below the summary, you'll see a "Description" text field where you can type a longer description of the changes in the commit, which is helpful when looking back at the history of a project and understanding why changes were made. Since you're making a basic update of a _README.md_ file, you can skip the description.
|
||||
|
||||
|
||||
5. Below your commit message, click **Commit to BRANCH NAME**. The commit button shows your current branch so you can be sure to commit to the branch you want.
|
||||
6. To push your changes to the remote repository on {% data variables.product.product_name %}, click **Push origin**.
|
||||
|
||||
@@ -95,9 +95,9 @@ Now that you've created and published your repository, you're ready to make chan
|
||||
- The **Push origin** button is the same one that you clicked to publish your repository to {% data variables.product.product_name %}. This button changes contextually based on where you are at in the Git workflow. It should now say `Push origin` with a `1` next to it, indicating that there is one commit that has not been pushed up to {% data variables.product.product_name %}.
|
||||
- The "origin" in **Push origin** means that you are pushing changes to the remote called `origin`, which in this case is your project's repository on {% data variables.product.prodname_dotcom_the_website %}. Until you push any new commits to {% data variables.product.product_name %}, there will be differences between your project's repository on your computer and your project's repository on {% data variables.product.prodname_dotcom_the_website %}. This allows you to work locally and only push your changes to {% data variables.product.prodname_dotcom_the_website %} when you're ready.
|
||||
7. In the window to the right of the **Changes** view, you'll see suggestions for actions you can do next. To open the repository on {% data variables.product.product_name %} in your browser, click **View on {% data variables.product.product_name %}**.
|
||||
|
||||
|
||||
8. In your browser, click **2 commits**. You'll see a list of the commits in this repository on {% data variables.product.product_name %}. The first commit should be the commit you just made in {% data variables.product.prodname_desktop %}.
|
||||
|
||||
|
||||
|
||||
## Conclusion
|
||||
You've now created a repository, published the repository to {% data variables.product.product_name %}, made a commit, and pushed your changes to {% data variables.product.product_name %}. You can follow this same workflow when contributing to other projects that you create or collaborate on.
|
||||
|
||||
@@ -42,7 +42,7 @@ After you have installed {% data variables.product.prodname_desktop %}, you can
|
||||
|
||||
1. Before you can authenticate to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}, you will need an account. For more information about creating an account, see "[AUTOTITLE](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" or contact your {% data variables.product.prodname_enterprise %} site administrator.
|
||||
2. In the File drop-down menu, click **Options**. In the options window, click **Accounts** and follow the steps to sign in. For more information on authenticating, see "[AUTOTITLE](/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop)."
|
||||
|
||||
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
|
||||
@@ -40,7 +40,7 @@ To troubleshoot this error, follow these steps.
|
||||
3. Right-click `com.github.GitHubClient.ShipIt` and then click **Get Info**.
|
||||
4. Click the arrow to the left of "Sharing & Permissions."
|
||||
5. If the Privilege to the right of your user account does not say "Read & Write," click the text and then click **Read & Write**.
|
||||
|
||||
|
||||
6. Open {% data variables.product.prodname_desktop %} and check for updates.
|
||||
|
||||
## Troubleshooting problems on Windows
|
||||
|
||||
@@ -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**.
|
||||
|
||||
|
||||
@@ -20,6 +20,6 @@ The {% data variables.product.prodname_community_exchange %} community moderates
|
||||
|
||||
1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
|
||||
1. Above the list of repositories, click the **Submissions** tab.
|
||||
|
||||
|
||||
1. Optionally, edit your submitted repository. To the right of the repository you want to edit, click {% octicon "pencil" aria-label="The edit icon" %} to go directly to your repository homepage. From there, you can update the purpose, topics, and offers assigned to your repository.
|
||||
1. Optionally, delete a submitted repository from the gallery. To the right of the repository submission you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
@@ -45,7 +45,7 @@ A good repository submission for both `Learn` and `Collaborate` purposes, is a r
|
||||
|
||||
1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
|
||||
1. Above the list of repositories, to the right of the search and dropdown filters, click **Add repository**.
|
||||
|
||||
|
||||
1. In the pop-up window, use the **What is the purpose of your submission?** drop-down menu and select one or more entries matching your submission.
|
||||
1. Use the **Which repository would you like to use?** drop-down menu and select the repository for your submission. If the submission criteria hasn't been met, you will be notified of the missing items, and you can click on **Edit your repository** if you want to view the repository and make changes to meet the criteria.
|
||||
1. Use the **Which offers did you use for your project?** drop-down menu and select one or more entries matching your submission.
|
||||
|
||||
@@ -30,7 +30,7 @@ You can unfollow an organization if you do not wish to see their {% ifversion fp
|
||||
{% data reusables.profile.navigate-to-user-profile %}
|
||||
2. Under the user's profile picture, click **following**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Further reading
|
||||
|
||||
@@ -36,7 +36,7 @@ You can unfollow someone if you do not wish to see their public activity on {% d
|
||||
{% data reusables.profile.navigate-to-user-profile %}
|
||||
1. Under the user's profile picture, click **following**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Viewing followers on {% data variables.product.product_name %}
|
||||
|
||||
|
||||
@@ -81,14 +81,14 @@ You can add a repository to an existing or new list wherever you see a repositor
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Find the repository you want to add to your list by typing it into the search bar.
|
||||
3. Next to the repository you want to add, use the **Starred** dropdown menu and select your list.
|
||||
|
||||
|
||||
|
||||
### Removing a repository from your list
|
||||
|
||||
{% data reusables.stars.stars-page-navigation %}
|
||||
2. Select your list.
|
||||
3. Next to the repository you want to remove, use the **Starred** drop-down menu and deselect your list.
|
||||
|
||||
|
||||
|
||||
### Editing a list name or description
|
||||
|
||||
|
||||
@@ -47,7 +47,7 @@ If you do not verify your email address, you will not be able to:
|
||||
{% data reusables.user-settings.emails %}
|
||||
1. Under your email address, click **Resend verification email**.
|
||||
|
||||
|
||||
|
||||
4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
|
||||
|
||||
## Troubleshooting email verification
|
||||
|
||||
@@ -33,7 +33,7 @@ You can enable a fixed-width font in every comment field on {% data variables.pr
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.appearance-settings %}
|
||||
1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -58,13 +58,13 @@ You can put a maximum of 2,500 cards into each project column. If a column has r
|
||||
|
||||
1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click the **Recent**, **Repository**, **User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to.
|
||||
3. Type the name of the project in **Filter projects** field.
|
||||
4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request.
|
||||
5. Click **Awaiting triage**{% octicon "triangle-down" aria-hidden="true" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -26,5 +26,5 @@ Automation in your {% data variables.projects.projects_v1_board %} does not appl
|
||||
|
||||
{% data reusables.project-management.click-menu %}
|
||||
2. Click {% octicon "kebab-horizontal" aria-label="Project menu" %}, then click **View archive**.
|
||||
|
||||
|
||||
3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**.
|
||||
|
||||
@@ -23,7 +23,7 @@ When you copy a project, the new project will contain the same views and custom
|
||||
1. Navigate to the project you want to copy.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %} to open the menu.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "copy" aria-hidden="true" %} **Make a copy**.
|
||||
1. Optionally, if you want all draft issues to be copied with the project, in the "Make a copy" dialog, select **Draft issues will be copied if selected**.
|
||||
|
||||
@@ -42,10 +42,10 @@ You can migrate your project boards to the new {% data variables.product.prodnam
|
||||
{% data reusables.projects.enable-migration %}
|
||||
1. In the top right corner of {% data variables.product.prodname_dotcom_the_website %}, click your profile photo, then click **Your projects**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-hidden="true" %} **Projects**.
|
||||
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ You can set the date or iteration fields that your roadmap will use to position
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "calendar" aria-hidden="true" %} **Date fields**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, to create a new date or iteration field, click {% octicon "plus" aria-hidden="true" %} **New field**, type the name of your field, and click **Save**. You can then select the new field or create another.
|
||||
1. Select a date or iteration field for "Start date" and "Target date."
|
||||
@@ -34,7 +34,7 @@ You can configure vertical markers on a roadmap to show your iterations, the dat
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "location" aria-hidden="true" %} **Markers**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the menu, select which markers you want to display on your roadmap.
|
||||
|
||||
@@ -46,7 +46,7 @@ You can choose the density of items on your roadmap. You can zoom in to show one
|
||||
|
||||
1. In the top right of your roadmap, click {% octicon "search" aria-label="The zoom icon next to Month, Quarter, or Year" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select either **Month**, **Quarter**, or **Year**.
|
||||
|
||||
|
||||
@@ -148,7 +148,7 @@ Next, configure the auto-add workflow to automatically add issues opened in a re
|
||||
Finally, add a built in workflow to set the status to **Todo** when an item is added to your project.
|
||||
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "workflow" aria-hidden="true" %} **Workflows**.
|
||||
1. Under **Default workflows**, click **Item added to project**.
|
||||
1. Next to **When**, ensure that both `issues` and `pull requests` are selected.
|
||||
|
||||
@@ -66,7 +66,7 @@ If you know the issue or pull request number or if you know part of the title, y
|
||||
You can add multiple issues and pull requests from your project and use filters, such as `label:bug`, to narrow down your search.
|
||||
|
||||
1. In the bottom row of the project, click {% octicon "plus" aria-hidden="true" %}.
|
||||
|
||||
|
||||
1. Click **Add item from repository**.
|
||||
{% data reusables.projects.bulk-add %}
|
||||
|
||||
@@ -93,7 +93,7 @@ You can also add an issue or pull request to your project from within the issue
|
||||
|
||||
1. Navigate to the issue or pull request that you want to add to a project.
|
||||
2. In the side bar, click **Projects**.
|
||||
|
||||
|
||||
3. Select the project that you want to add the issue or pull request to.
|
||||
4. Optionally, populate the custom fields.
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ You can archive an item to keep the context about the item in the project but re
|
||||
1. Navigate to your project.
|
||||
1. In the top-right, click {% octicon "kebab-horizontal" aria-label="More options" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the menu, click {% octicon "archive" aria-hidden="true" %} **Archived items**.
|
||||
1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)."
|
||||
|
||||
@@ -17,14 +17,14 @@ You can copy the contents of one cell and paste the contents into multiple other
|
||||
1. Navigate to a project view that is using the table layout.
|
||||
1. Select the cell that you would like to copy.
|
||||
|
||||
|
||||
|
||||
|
||||
1. To copy the contents of the selected cell, press <kbd>Command</kbd>+<kbd>C</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>C</kbd> (Windows.)
|
||||
1. Select the destination cells for the copied content.
|
||||
|
||||
{% indented_data_reference reusables.projects.select-a-cell spaces=4 %}
|
||||
|
||||
|
||||
|
||||
|
||||
1. To paste the previously copied content, press <kbd>Command</kbd>+<kbd>V</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>V</kbd> (Windows.)
|
||||
|
||||
@@ -36,15 +36,15 @@ You can quickly copy one cell's content over other cells in the same field by dr
|
||||
1. Select the cell that you would like to copy.
|
||||
1. If it's possible to copy the cell's content, a blue handle will be shown on the lower right of the selected cell.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Drag the handle up or down over the cells where you would like to copy the contents.
|
||||
|
||||
|
||||
|
||||
|
||||
1. When you finish dragging, the contents of the originally selected cell will be copied over the cells you selected while dragging.
|
||||
|
||||
|
||||
|
||||
|
||||
## Clearing the content of multiple table cells
|
||||
|
||||
@@ -55,7 +55,7 @@ You can quickly clear the same field for multiple items.
|
||||
|
||||
{% indented_data_reference reusables.projects.select-a-cell spaces=4 %}
|
||||
|
||||
|
||||
|
||||
|
||||
1. Press <kbd>Delete</kbd> or <kbd>Backspace</kbd> on your keyboard.
|
||||
|
||||
@@ -66,4 +66,4 @@ When you make a bulk change in the table layout, {% data variables.product.produ
|
||||
1. Make a bulk change to your table.
|
||||
1. When the notice appears in the lower right of your table, click **Undo**.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ You can filter issues and pull requests to find:
|
||||
{% data reusables.repositories.sidebar-issue-pr %}
|
||||
3. Above the list, select the **Filters** dropdown menu, then click the type of filter you're interested in.
|
||||
|
||||
|
||||
|
||||
|
||||
## Filtering issues and pull requests by assignees
|
||||
|
||||
@@ -213,7 +213,7 @@ You can sort any filtered view by:
|
||||
{% data reusables.repositories.sidebar-issue-pr %}
|
||||
1. Above the list of issues or pull requests, select the **Sort** dropdown menu, then click a sort method.
|
||||
|
||||
|
||||
|
||||
|
||||
To clear your sort selection, click **Sort** > **Newest**.
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ shortTitle: Add to milestones
|
||||
|
||||
1. Above the list of issues or pull requests, select the **Milestone** dropdown menu.
|
||||
|
||||
|
||||
|
||||
1. In the "Filter milestones" field, start typing the name of an existing milestone, then click the milestone's name to associate it with the item.
|
||||
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ shortTitle: Filter by milestone
|
||||
{% data reusables.repositories.sidebar-issue-pr %}
|
||||
3. Select **Milestones** to see a list of all available milestones for the repository.
|
||||
|
||||
|
||||
|
||||
4. Select the milestone you're interested in from the list. You can view relevant information for the milestone, including all issues and pull requests associated with it, from the milestone page. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones)."
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -19,7 +19,7 @@ shortTitle: View progress to milestone
|
||||
{% data reusables.repositories.sidebar-issue-pr %}
|
||||
1. In the upper-left corner, click **Milestones**.
|
||||
|
||||
|
||||
|
||||
1. Click the milestone you wish to see more information about.
|
||||
|
||||
To better manage your project, you can prioritize issues or pull requests within a milestone. For more information, see "[AUTOTITLE](/issues/using-labels-and-milestones-to-track-work/about-milestones#prioritizing-issues-and-pull-requests-in-milestones)."
|
||||
|
||||
@@ -112,7 +112,7 @@ After you've initialized a Git repository, you can push the repository to {% dat
|
||||
{% data reusables.migrations.create-empty-repo %}
|
||||
1. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
|
||||
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. Change the current working directory to your local project.
|
||||
1. In the Command prompt, [add the URL for the remote repository](/get-started/getting-started-with-git/managing-remote-repositories) where your local repository will be pushed.
|
||||
|
||||
@@ -25,4 +25,4 @@ An organization's news feed shows other people's activity on repositories owned
|
||||
1. Open your {% data reusables.user-settings.personal_dashboard %}.
|
||||
1. In the upper-left corner of the page, select the dropdown menu that switches account context, then select an organization.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -55,7 +55,7 @@ With dependency insights you can view vulnerabilities, licenses, and other impor
|
||||
1. In the "Insights" sidebar, click **Dependencies**.
|
||||
1. Optionally, to view dependency insights for all your organizations, click **My organizations**.
|
||||
|
||||
|
||||
|
||||
1. To filter by a vulnerability status, a license, or a combination of the two, click the results in the **Open security advisories** and **Licenses** graphs.
|
||||
1. To see which dependents in your organization are using each library, next to a vulnerability, click {% octicon "package" aria-hidden-"true" %} **X dependents**.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ shortTitle: Manage a team discussion
|
||||
{% data reusables.organizations.team-discussions-tab %}
|
||||
6. Click {% octicon "kebab-horizontal" aria-label="The edit icon" %} next to the team discussion you want to edit or delete.
|
||||
7. Click **Edit**. Optionally, click **Delete**.
|
||||
|
||||
|
||||
8. Modify the team discussion title and comment as needed, and click **Update comment**.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -62,7 +62,7 @@ To help the person you're removing from your organization transition and help en
|
||||
{% data reusables.organizations.people %}
|
||||
1. Select the member or members you'd like to remove from the organization.
|
||||
|
||||
|
||||
|
||||
1. Above the list of members, select the **X members selected...** dropdown menu, and click **Remove from organization**.
|
||||
|
||||
|
||||
|
||||
@@ -95,4 +95,4 @@ To verify a domain, you must have access to modify domain records with your doma
|
||||
{% data reusables.organizations.verified-domains %}
|
||||
1. To the right of the domain to remove, select the {% octicon "kebab-horizontal" aria-label="Show more options" %} dropdown menu, then click **Delete**.
|
||||
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ If your organization is owned by an enterprise account, any enterprise owner can
|
||||
{% data reusables.organizations.people %}
|
||||
1. Select the person or people you'd like to promote to owner.
|
||||
|
||||
|
||||
|
||||
1. Above the list of members, select the **X members selected...** dropdown menu and click **Change role**.
|
||||
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ To create a new repository role, you add permissions to an inherited role and gi
|
||||
{% data reusables.organizations.org-settings-repository-roles %}
|
||||
1. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="Show custom role actions" %}, then click **Edit**.
|
||||
|
||||
|
||||
|
||||
1. Edit, then click **Update role**.
|
||||
|
||||
## Deleting a repository role
|
||||
|
||||
@@ -51,7 +51,7 @@ When you convert an organization member to an outside collaborator, their privil
|
||||
{% data reusables.organizations.people %}
|
||||
1. Select the person or people you'd like to convert to outside collaborators.
|
||||
|
||||
|
||||
|
||||
1. Above the list of members, select the **X members selected...** dropdown menu and click **Convert to outside collaborator**.
|
||||
|
||||
|
||||
|
||||
@@ -144,7 +144,7 @@ After you configure the apex domain, you must configure a CNAME record with your
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain," click **Remove**.
|
||||
|
||||
|
||||
|
||||
## Securing your custom domain
|
||||
|
||||
|
||||
@@ -35,10 +35,10 @@ shortTitle: Configure publishing source
|
||||
|
||||
{% else %}
|
||||
1. Under "{% data variables.product.prodname_pages %}", use the branch dropdown menu and select a publishing source.
|
||||
|
||||
|
||||
{% endif %}
|
||||
1. Optionally, use the folder dropdown menu to select a folder for your publishing source.
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
### Troubleshooting publishing from a branch
|
||||
|
||||
@@ -41,7 +41,7 @@ Unpublishing a site does not permanently delete the site. For information on del
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.pages.sidebar-pages %}
|
||||
5. Under "{% data variables.product.prodname_pages %}", use the branch dropdown menu and select **None.**
|
||||
|
||||
|
||||
{% data reusables.pages.update_your_dns_settings %}
|
||||
|
||||
## Unpublishing a user or organization site
|
||||
|
||||
@@ -145,7 +145,7 @@ gh pr create --web
|
||||
|
||||
1. Confirm that the branch in the **base:** dropdown menu is the branch where you want to merge your changes.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data variables.product.prodname_desktop %} will advise you whether the current branch can be automatically merged into the base branch.
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ You can request a review from either a suggested or specific person. Suggested r
|
||||
1. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.
|
||||
1. To request a review from a suggested person under **Reviewers**, next to their username, click **Request**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, to request a review from someone other than a suggested person, click **Reviewers**.
|
||||
|
||||
@@ -43,7 +43,7 @@ You can request a review from either a suggested or specific person. Suggested r
|
||||
|
||||
1. After your pull request is reviewed and you've made the necessary changes, you can ask a reviewer to re-review your pull request. Navigate to **Reviewers** in the right sidebar and click {% octicon "sync" aria-label="Re-request review" %} next to the reviewer's name whose review you'd like.
|
||||
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -52,7 +52,7 @@ You can search for archived repositories. For more information, see "[AUTOTITLE]
|
||||
3. Under "Danger Zone", click **Archive this repository**
|
||||
4. Read the warnings.
|
||||
5. In the text field, type the name of the repository you want to archive.
|
||||
|
||||
|
||||
6. Click **I understand the consequences, archive this repository**.
|
||||
|
||||
## Unarchiving a repository
|
||||
|
||||
@@ -48,11 +48,11 @@ When creating a topic:
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. In the top right corner of the page, to the right of "About", click {% octicon "gear" aria-label="Edit repository metadata" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Under "Topics", start to type the topic you want to add to your repository to display a dropdown menu of any matching topics. Click the topic you want to add or continue typing to create a new topic.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Optional, if there are "Suggested" topics displayed under the "Topics" field, click {% octicon "plus" aria-label="Add this topic" %} to add or {% octicon "dash" aria-label="Decline this topic" %} to decline the suggested topic.
|
||||
5. After you've finished adding topics, click **Save changes**.
|
||||
@@ -41,7 +41,7 @@ This procedure demonstrates how to configure autolinks to reference external res
|
||||
{% endif %}
|
||||
1. At the top right of the page, click **Add autolink reference**.
|
||||
|
||||
|
||||
|
||||
{% ifversion autolink-reference-alphanumeric %}
|
||||
1. Select the format of the reference identifier used in the external resource, either **Alphanumeric** or **Numeric**.
|
||||
{% endif %}
|
||||
|
||||
@@ -28,7 +28,6 @@ shortTitle: Connections between repositories
|
||||
|
||||
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -30,9 +30,9 @@ You can also see a list of people who have contributed to the project's Python d
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Contributors**.
|
||||
|
||||
|
||||
4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
|
||||
|
||||
|
||||
|
||||
## Troubleshooting contributors
|
||||
|
||||
|
||||
@@ -57,7 +57,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,15 +28,15 @@ topics:
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. In the file tree view, click the {% octicon "filter" aria-hidden="true" %} **Jump to file** search bar. You can also find the {% octicon "filter" aria-hidden="true" %} **Jump to file** search bar at the top of the integrated file editor.
|
||||
|
||||
|
||||
|
||||
1. In the search bar, type the name of the file or directory you'd like to find.
|
||||
1. In the list of results, click the file or directory you wanted to find. You can view the file path for a directory or file below each search result.
|
||||
{% else %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Above the list of files, click **Go to file**.
|
||||
|
||||
|
||||
1. In the search field, type the name of the file you'd like to find.
|
||||
|
||||
|
||||
1. In the list of results, click the file you wanted to find.
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ You can find apps and actions on {% data variables.product.prodname_marketplace
|
||||
## Searching in {% data variables.product.prodname_marketplace %}
|
||||
|
||||
1. At the top of any page, click **Marketplace**.
|
||||
|
||||
|
||||
2. Type any keywords and press **Enter**.
|
||||
3. Optionally, filter your results by clicking one or more options in the left sidebar.
|
||||
|
||||
@@ -32,7 +32,7 @@ Anytime you search across all of {% data variables.product.prodname_dotcom_the_w
|
||||
1. Navigate to https://github.com/search.
|
||||
2. Type any keywords and press **Enter**.
|
||||
3. In the left sidebar, click **Marketplace**.
|
||||
|
||||
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -81,6 +81,6 @@ If you transfer a repository that has been added to a sponsorship tier, sponsors
|
||||
1. Select **Grant sponsors access to a private repository**.
|
||||
1. Select the dropdown menu that appears and click the repository you want to add.
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.sponsors.tier-update %}
|
||||
|
||||
@@ -32,8 +32,8 @@ Once you navigate to the "Join the waitlist" profile setup page for the account
|
||||
1. Under "How you receive payouts" or "Organization bank account", select the **Use a fiscal host** or **This organization is using a fiscal host** option.
|
||||
1. Use the **Select a fiscal host** dropdown to choose the fiscal host you want to use.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the text box under "Fiscal host project profile URL", type the URL to your profile page on the fiscal host's site. This helps us verify that you are indeed registered with the fiscal host.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -47,7 +47,7 @@ For example, you can use `https://github.com/sponsors/{account}?metadata_campaig
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
1. Optionally, to filter your sponsors by tier, use the **Filter** drop-down menu, click **Active tiers** or **Retired tiers**, and select a tier.
|
||||
|
||||
|
||||
|
||||
|
||||
## Viewing recent sponsorship activity
|
||||
|
||||
|
||||
@@ -18,11 +18,11 @@ shortTitle: Attribute sponsorships
|
||||
1. Navigate to the organization whose sponsorships you want to attribute to another organization.
|
||||
1. Under your organization name, click {% octicon "heart" aria-hidden="true" %} **Sponsoring**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the sidebar, click {% octicon "gear" aria-hidden="true" %} **Settings**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the "Link sponsorships to another account" section, select the dropdown menu, then click the organization you want your organization's sponsorships to be attributed to.
|
||||
1. Click **Link account**.
|
||||
|
||||
@@ -102,7 +102,7 @@ Before you can sponsor an account, you must have a verified email address. For m
|
||||
If you are a member of multiple organizations, to see all of your organizations, click **See more** {% octicon "triangle-down" aria-label="The downwards-facing triangle icon" %}.
|
||||
1. Optionally, to download a CSV file of developers who maintain your account's or organization's dependencies, click **results as CSV**.
|
||||
|
||||
|
||||
|
||||
|
||||
To sponsor these maintainers using the downloaded file, in the corresponding cells of the "Sponsorship amount in USD" column, input sponsorship amounts in US dollars for each maintainer you want to sponsor.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user