зеркало из https://github.com/github/docs.git
Merge branch 'main' into patch-1
This commit is contained in:
Laura Coursen
GitHub
Коммит
40d6826b53
Двоичные данные
assets/images/help/docs/version-picker.png
Двоичные данные
assets/images/help/docs/version-picker.png
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 40 KiB После Ширина: | Высота: | Размер: 101 KiB |
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 13 KiB |
|
|
@ -41,3 +41,4 @@ children:
|
|||
- /setting-up-and-managing-your-github-profile
|
||||
- /managing-subscriptions-and-notifications-on-github
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -63,3 +63,4 @@ children:
|
|||
- /creating-actions
|
||||
- /guides
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Approving workflow runs from private forks
|
||||
intro: 'When someone without write access submits a pull request to a private repository, a maintainer may need to approve any workflow runs.'
|
||||
permissions: 'Maintainers with write access to a repository can approve workflow runs.'
|
||||
permissions: Maintainers with write access to a repository can approve workflow runs.
|
||||
versions:
|
||||
feature: actions-private-fork-workflow-approvals
|
||||
shortTitle: Approve private fork runs
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Downloading workflow artifacts
|
||||
intro: You can download archived artifacts before they automatically expire.
|
||||
permissions: People who are signed into {% data variables.product.product_name %} and have read access to a repository can download workflow artifacts.
|
||||
permissions: 'People who are signed into {% data variables.product.product_name %} and have read access to a repository can download workflow artifacts.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ topics:
|
|||
- Migration
|
||||
- CI
|
||||
- CD
|
||||
shortTitle: Automate migration with {% data variables.product.prodname_actions_importer %}
|
||||
shortTitle: 'Automate migration with {% data variables.product.prodname_actions_importer %}'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ redirect_from:
|
|||
- /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
|
||||
- /actions/reference/encrypted-secrets
|
||||
- /actions/managing-workflows/storing-secrets
|
||||
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: Required workflows
|
||||
shortTitle: Required workflows
|
||||
intro: "You can specify which workflows will run as required status checks in all repositories or selected repositories in your organization."
|
||||
intro: You can specify which workflows will run as required status checks in all repositories or selected repositories in your organization.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: 'required-workflows'
|
||||
feature: required-workflows
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
|
|
@ -52,4 +52,4 @@ After a required workflow has run at least once in a repository, you can view it
|
|||
|
||||
## Adding a required workflow to an organization
|
||||
|
||||
Organization owners can configure required workflows in their organization. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#adding-a-required-workflow-to-an-organization)."
|
||||
Organization owners can configure required workflows in their organization. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#adding-a-required-workflow-to-an-organization)."
|
||||
|
|
|
|||
|
|
@ -20,3 +20,4 @@ children:
|
|||
- /configuring-dependency-review-for-your-appliance
|
||||
- /configuring-secret-scanning-for-your-appliance
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -21,3 +21,4 @@ children:
|
|||
- /replacing-a-cluster-node
|
||||
- /evacuating-a-cluster-node
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Enabling GitHub Actions with Google Cloud Storage
|
|||
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Google Cloud Storage to store data generated by workflow runs.'
|
||||
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
||||
versions:
|
||||
feature: 'actions-ghes-gcp-storage'
|
||||
feature: actions-ghes-gcp-storage
|
||||
type: how_to
|
||||
topics:
|
||||
- Actions
|
||||
|
|
|
|||
|
|
@ -148,3 +148,4 @@ includeGuides:
|
|||
- /admin/overview/creating-an-enterprise-account
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: About {% data variables.product.prodname_emus %}
|
||||
title: 'About {% data variables.product.prodname_emus %}'
|
||||
shortTitle: About managed users
|
||||
intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
|
||||
redirect_from:
|
||||
|
|
|
|||
|
|
@ -77,4 +77,4 @@ To configure provisioning, follow the appropriate link from the table below.
|
|||
|
||||
**Note:** Azure AD does not support provisioning nested groups. For more information, see [How Application Provisioning works in Azure Active Directory](https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#assignment-based-scoping).
|
||||
|
||||
{% endnote %}
|
||||
{% endnote %}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Migrating your enterprise to a new identity provider or tenant
|
||||
shortTitle: Migrate to new IdP or tenant
|
||||
intro: 'You can migrate your enterprise to a different identity provider (IdP) or Azure AD tenant.'
|
||||
intro: You can migrate your enterprise to a different identity provider (IdP) or Azure AD tenant.
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
versions:
|
||||
feature: idp-tenant-migration
|
||||
|
|
@ -55,4 +55,4 @@ To migrate to a new IdP or tenant, you cannot edit your existing SAML configurat
|
|||
|
||||
## Migrating when the normalized SCIM `userName` values will change
|
||||
|
||||
If the normalized SCIM `userName` values will change, {% data variables.product.company_short %} must provision a new enterprise account for your migration. [Contact our sales team](https://github.com/enterprise/contact) for help.
|
||||
If the normalized SCIM `userName` values will change, {% data variables.product.company_short %} must provision a new enterprise account for your migration. [Contact our sales team](https://github.com/enterprise/contact) for help.
|
||||
|
|
|
|||
|
|
@ -182,4 +182,4 @@ After you enable SCIM on a {% data variables.product.product_name %} instance, a
|
|||
| :- | :- | :- | :- |
|
||||
| URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.product_name %} | <nobr><code>{% data variables.product.api_url_pre %}/scim/v2</nobr></code> |
|
||||
| Shared secret | {% data variables.product.pat_generic_caps %}, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | {% data variables.product.pat_generic_caps %} you created in step 1 |
|
||||
{%- endif %}
|
||||
{%- endif %}
|
||||
|
|
|
|||
|
|
@ -126,3 +126,4 @@ children:
|
|||
- /release-notes
|
||||
- /all-releases
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -101,4 +101,4 @@ AP | `ghe_stats.users.suspended_users` | Number of user accounts that are suspen
|
|||
|
||||
To see an example of the headings included in the CSV export for {% data variables.product.prodname_server_statistics %}, download the [{% data variables.product.prodname_server_statistics %} CSV example](/assets/server-statistics-csv-example.csv).
|
||||
|
||||
To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)."
|
||||
To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)."
|
||||
|
|
|
|||
|
|
@ -139,4 +139,4 @@ Using the qualifier `country`, you can filter events in the audit log based on t
|
|||
### Search based on the token that performed the action
|
||||
|
||||
Use the `hashed_token` qualifier to search based on the token that performed the action. Before you can search for a token, you must generate a SHA-256 hash. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Using the audit log API for your enterprise
|
||||
intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.'
|
||||
intro: You can programmatically retrieve enterprise events with the REST or GraphQL API.
|
||||
shortTitle: Audit log API
|
||||
permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
|
|
|
|||
|
|
@ -15,8 +15,6 @@ topics:
|
|||
|
||||
{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with security and access controls, workflow automation, and policy enforcement.
|
||||
|
||||
{% data reusables.enterprise.about-github-for-enterprises %}
|
||||
|
||||
## A highly available and planet-scale cloud
|
||||
|
||||
{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: About GitHub Enterprise Cloud
|
||||
intro: "{% data reusables.enterprise.about-ghec %}"
|
||||
intro: '{% data reusables.enterprise.about-ghec %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
type: overview
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ intro: 'Businesses can use {% data variables.product.prodname_dotcom %}''s enter
|
|||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Enterprise
|
||||
|
|
@ -29,12 +28,7 @@ Optionally, you can add extra code security features with {% data variables.prod
|
|||
|
||||
For {% data variables.product.prodname_ghe_cloud %}, you can allow developers to create and manage their own personal accounts, or you can use {% data variables.product.prodname_emus %}, which enables you to create and manage the user accounts for your developers. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
|
||||
|
||||
{% data variables.product.prodname_ghe_managed %} is in limited availability for select customers with stringent security and compliance requirements. For more information, see "[About {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/overview/about-github-ae){% ifversion not ghae %}" in the {% data variables.product.prodname_ghe_managed %} documentation.{% else %}."{% endif %}
|
||||
|
||||
You can benefit from the power of {% data variables.product.prodname_dotcom_the_website %} even while using {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} by enabling {% data variables.product.prodname_github_connect %}, which allows you to configure additional features and workflows such as {% data variables.product.prodname_dependabot_alerts %} for insecure dependencies.{% ifversion ghec %}
|
||||
|
||||
- "[About {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
|
||||
- "[About {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation{% else %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."{% endif %}
|
||||
You can benefit from the power of {% data variables.product.prodname_dotcom_the_website %} even while using {% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %} by enabling {% data variables.product.prodname_github_connect %}, which allows you to configure additional features and workflows such as {% data variables.product.prodname_dependabot_alerts %} for insecure dependencies. For more information, see "[About {% data variables.product.prodname_github_connect %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/about-github-connect){% ifversion ghes or ghae %}."{% elsif ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Best practices for enterprises
|
||||
shortTitle: Best practices
|
||||
intro: Learn {% data variables.product.company_short %}-recommended practices for your enterprise.
|
||||
intro: 'Learn {% data variables.product.company_short %}-recommended practices for your enterprise.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -46,4 +46,4 @@ You can manage the display of usernames within your enterprise's private reposit
|
|||
## Further reading
|
||||
|
||||
- "[Best practices for repositories](/repositories/creating-and-managing-repositories/best-practices-for-repositories)"
|
||||
- "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)"
|
||||
- "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)"
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Enforcing policies for GitHub Copilot in your enterprise
|
||||
intro: 'You can enforce policies for {% data variables.product.prodname_copilot_for_business %} within your enterprise''s organizations, or allow policies to be set in each organization.'
|
||||
permissions: Enterprise owners can enforce policies for {% data variables.product.prodname_copilot_for_business %} in an enterprise.
|
||||
permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_copilot_for_business %} in an enterprise.'
|
||||
product: '{% data reusables.gated-features.copilot-billing %}'
|
||||
versions:
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Adding organizations to your enterprise
|
||||
intro: You can add organizations to manage within your enterprise by creating a new organization, inviting an existing organization, or transferring an organization from a different enterprise account.
|
||||
intro: 'You can add organizations to manage within your enterprise by creating a new organization, inviting an existing organization, or transferring an organization from a different enterprise account.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
|
||||
- /articles/adding-organizations-to-your-enterprise-account
|
||||
|
|
|
|||
|
|
@ -39,3 +39,4 @@ children:
|
|||
- /rebuilding-contributions-data
|
||||
shortTitle: Manage users
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Managing organization members in your enterprise
|
||||
intro: 'You can add or remove members from an organization in bulk.'
|
||||
intro: You can add or remove members from an organization in bulk.
|
||||
permissions: Enterprise owners can add or remove organization members in bulk.
|
||||
versions:
|
||||
feature: enterprise-manage-organization-members
|
||||
|
|
@ -41,4 +41,4 @@ Members can also be added or removed from an organization at the organization le
|
|||
|
||||
|
||||
|
||||
4. Optionally, to add or remove multiple users at the same time, select multiple checkboxes. Use the dropdown to select **Add to organizations** or **Remove from organizations**.
|
||||
4. Optionally, to add or remove multiple users at the same time, select multiple checkboxes. Use the dropdown to select **Add to organizations** or **Remove from organizations**.
|
||||
|
|
|
|||
|
|
@ -54,4 +54,4 @@ If you have multiple keys or are attempting to sign commits or tags with a key t
|
|||
|
||||
* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
|
||||
* "[Signing tags](/articles/signing-tags)"{% ifversion fpt or ghec %}
|
||||
* "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)"{% endif %}
|
||||
* "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)"{% endif %}
|
||||
|
|
|
|||
|
|
@ -55,3 +55,4 @@ children:
|
|||
- /managing-billing-for-git-large-file-storage
|
||||
- /setting-up-paid-organizations-for-procurement-companies
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -9,3 +9,4 @@ children:
|
|||
- /managing-your-github-copilot-for-individuals-subscription
|
||||
- /viewing-your-github-copilot-usage
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -39,4 +39,4 @@ The spending information will display the total spending for each organization f
|
|||
1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
|
||||
1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -92,4 +92,4 @@ To avoid reaching your spending limit in the current billing cycle, you can dele
|
|||
|
||||
For more information about managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)."
|
||||
|
||||
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
|
||||
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
|
||||
|
|
|
|||
|
|
@ -30,3 +30,4 @@ children:
|
|||
- /running-codeql-code-scanning-in-a-container
|
||||
- /viewing-code-scanning-logs
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Troubleshooting {% ifversion code-scanning-without-workflow %}your advanced setup for CodeQL{% else %}the CodeQL workflow{% endif %}
|
||||
shortTitle: Troubleshoot {% ifversion code-scanning-without-workflow %}advanced setup{% else %}CodeQL workflow{% endif %}
|
||||
title: 'Troubleshooting {% ifversion code-scanning-without-workflow %}your advanced setup for CodeQL{% else %}the CodeQL workflow{% endif %}'
|
||||
shortTitle: 'Troubleshoot {% ifversion code-scanning-without-workflow %}advanced setup{% else %}CodeQL workflow{% endif %}'
|
||||
intro: 'If you''re having problems with {% ifversion code-scanning-without-workflow %}advanced setup for {% data variables.product.prodname_code_scanning %}{% else %}{% data variables.product.prodname_code_scanning %} setup{% endif %}, you can troubleshoot by using these tips for resolving issues.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
|
|
|
|||
|
|
@ -31,4 +31,4 @@ If enabling your default setup is taking too long, try canceling the workflow ru
|
|||
|
||||
## Unclear what triggered a workflow run
|
||||
|
||||
If you don't know what triggered an analysis, look at the log for the last scan. For more information on viewing your last scan's log, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#viewing-the-logging-output-from-code-scanning)."
|
||||
If you don't know what triggered an analysis, look at the log for the last scan. For more information on viewing your last scan's log, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#viewing-the-logging-output-from-code-scanning)."
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Query reference files
|
||||
intro: 'You can use query reference files to define the location of a query you want to run in tests.'
|
||||
intro: You can use query reference files to define the location of a query you want to run in tests.
|
||||
product: '{% data reusables.gated-features.codeql %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
|
|||
|
|
@ -98,9 +98,47 @@ The file is successfully uploaded as both absolute URIs use the same URI scheme
|
|||
|
||||
<!--UI-LINK: When code scanning fails, the error banner shown in the Security > Code scanning alerts view links to this anchor.-->
|
||||
|
||||
You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/).
|
||||
You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/).
|
||||
|
||||
{% data reusables.code-scanning.upload-sarif-alert-limit %}
|
||||
For each `gzip`-compressed SARIF file, SARIF upload supports a maximum size of 10 MB. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries.
|
||||
|
||||
{% data variables.product.prodname_code_scanning_capc %} supports uploading a maximum number of entries for the data objects in the following table. If any of these objects exceeds its maximum value the SARIF file is rejected. For some objects, there is an additional limit on the number of values that will be displayed. Whenever possible the most important values are shown. To get the most out of your analysis when it includes data above the supported limits, try to optimize the analysis configuration (for example, for the CodeQL tool, identify and disable the most noisy queries).
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.8 %}
|
||||
|
||||
| **SARIF data** | **Maximum values** | **Additional limits** |
|
||||
|----------------------------------|:------------------:|----------------------------------------------------------------------------------|
|
||||
| Runs per file | 20 | |
|
||||
| Results per run | 25,000 | Only the top 5,000 results will be included, prioritized by severity. |
|
||||
| Rules per run | 25,000 | |
|
||||
| Tool extensions per run | 100 | |
|
||||
| Thread Flow Locations per result | 10,000 | Only the top 1,000 Thread Flow Locations will be included, using prioritization. |
|
||||
| Location per result | 1,000 | Only 100 locations will be included. |
|
||||
| Tags per rule | 20 | Only 10 tags will be included. |
|
||||
|
||||
{% elsif ghes < 3.9 %}
|
||||
|
||||
| **SARIF data** | **Maximum values** | **Additional limits** |
|
||||
|----------------------------------|:------------------:|----------------------------------------------------------------------------------|
|
||||
| Runs per file | 15 | |
|
||||
| Results per run | 25,000 | Only the top 5,000 results will be included, prioritized by severity. |
|
||||
| Rules per run | 25,000 | |
|
||||
| Tool extensions per run | 100 | |
|
||||
| Thread Flow Locations per result | 10,000 | Only the top 1,000 Thread Flow Locations will be included, using prioritization. |
|
||||
| Location per result | 1,000 | Only 100 locations will be included. |
|
||||
| Tags per rule | 20 | Only 10 tags will be included. |
|
||||
|
||||
{% else %}
|
||||
|
||||
| **SARIF data** | **Maximum values** | **Additional limits** |
|
||||
|----------------------------------|:------------------:|----------------------------------------------------------------------------------|
|
||||
| Runs per file | 15 | |
|
||||
| Results per run | 25,000 | Only the top 5,000 results will be included, prioritized by severity. |
|
||||
| Rules per run | 25,000 | |
|
||||
| Thread Flow Locations per result | 10,000 | Only the top 1,000 Thread Flow Locations will be included, using prioritization. |
|
||||
| Location per result | 1,000 | Only 100 locations will be included. | |
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Supported SARIF output file properties
|
||||
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@ title: Creating CodeQL databases
|
|||
intro: 'You can build a {% data variables.product.prodname_codeql %} database containing the data needed to query your code.'
|
||||
product: '{% data reusables.gated-features.codeql %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Advanced Security
|
||||
- Code scanning
|
||||
|
|
|
|||
|
|
@ -23,4 +23,5 @@ children:
|
|||
- /creating-and-working-with-codeql-packs
|
||||
- /publishing-and-using-codeql-packs
|
||||
- /specifying-command-options-in-a-codeql-configuration-file
|
||||
---
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Testing query help files
|
||||
intro: You can use the {% data variables.product.prodname_codeql_cli %} to preview your query help files as Markdown and ensure they are valid.
|
||||
intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to preview your query help files as Markdown and ensure they are valid.'
|
||||
product: '{% data reusables.gated-features.codeql %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
|
|||
|
|
@ -346,4 +346,4 @@ Add the private registry url to the `[[tool.poetry.source]]` section of the `pyp
|
|||
name = "private"
|
||||
url = "https://private_registry_url"
|
||||
default = true
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -93,3 +93,4 @@ includeGuides:
|
|||
- /code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api
|
||||
- /code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -59,3 +59,4 @@ children:
|
|||
- /security-overview
|
||||
- /guides
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -212,4 +212,4 @@ When you save a change to a custom pattern, this closes all the {% data variable
|
|||
1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
|
||||
1. Click **Yes, delete this pattern**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -81,4 +81,4 @@ The {% data variables.product.prodname_advisory_database %} uses the CVSS levels
|
|||
## Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"
|
||||
- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
|
||||
- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
|
||||
|
|
|
|||
|
|
@ -42,4 +42,4 @@ When a security researcher reports a vulnerability privately, you are notified a
|
|||
For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
|
||||
- Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,8 @@ topics:
|
|||
- Repositories
|
||||
- CVEs
|
||||
children:
|
||||
- /global-security-advisories
|
||||
- /repository-security-advisories
|
||||
- /guidance-on-reporting-and-writing
|
||||
---
|
||||
- /global-security-advisories
|
||||
- /repository-security-advisories
|
||||
- /guidance-on-reporting-and-writing
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Configuring private vulnerability reporting for a repository
|
||||
intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
|
||||
permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
|
||||
permissions: Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Performing a full rebuild of a container
|
||||
intro: If you are low on disk space, or want to ensure your dev container configuration will work in new codespaces, you can perform a full rebuild of a container.
|
||||
intro: 'If you are low on disk space, or want to ensure your dev container configuration will work in new codespaces, you can perform a full rebuild of a container.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -53,4 +53,4 @@ ln -sf $PWD/.devcontainer/config $HOME/config && set +x
|
|||
```
|
||||
|
||||
## Further reading
|
||||
- [Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)
|
||||
- [Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)
|
||||
|
|
|
|||
|
|
@ -117,4 +117,4 @@ Any additional {% data variables.product.prodname_vscode_shortname %} extensions
|
|||
|
||||
#### Using Settings Sync
|
||||
|
||||
{% data variables.product.prodname_vscode_shortname %}'s Settings Sync can allow potentially malicious content to transfer across devices. If you're creating a codespace for a repository whose contents you do not trust, you should open the codespace in the browser and leave Settings Sync disabled.
|
||||
{% data variables.product.prodname_vscode_shortname %}'s Settings Sync can allow potentially malicious content to transfer across devices. If you're creating a codespace for a repository whose contents you do not trust, you should open the codespace in the browser and leave Settings Sync disabled.
|
||||
|
|
|
|||
|
|
@ -92,4 +92,4 @@ To use {% data variables.product.prodname_copilot %} in a codespace in your JetB
|
|||
|
||||
- "[Getting started with GitHub Copilot in a JetBrains IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide)"
|
||||
|
||||
{% endjetbrains %}
|
||||
{% endjetbrains %}
|
||||
|
|
|
|||
|
|
@ -124,4 +124,4 @@ You can also personalize {% data variables.product.prodname_github_codespaces %}
|
|||
## Further reading
|
||||
|
||||
* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
|
||||
* "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)"
|
||||
* "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)"
|
||||
|
|
|
|||
|
|
@ -75,4 +75,4 @@ You can change the display name for your codespace on {% data variables.product.
|
|||
|
||||
1. In the prompt, under "Change display name to..." type your desired display name and click **OK**.
|
||||
|
||||
{% endwebui %}
|
||||
{% endwebui %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Creating a codespace from a template
|
||||
intro: If you're starting a new project, you can create a codespace from a blank template or choose a template specially designed for the type of work you want to do.
|
||||
intro: 'If you''re starting a new project, you can create a codespace from a blank template or choose a template specially designed for the type of work you want to do.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -101,4 +101,4 @@ Some software requires you to install NVIDIA CUDA to use your codespace’s GPU.
|
|||
|
||||
You can open your codespace in JupyterLab from the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces), or by using {% data variables.product.prodname_cli %}. For more information, see "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)."
|
||||
|
||||
{% data reusables.codespaces.jupyterlab-installed-in-codespace %}
|
||||
{% data reusables.codespaces.jupyterlab-installed-in-codespace %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Developing in a codespace
|
||||
intro: 'Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use your codespace in the browser or in a choice of code editors.'
|
||||
intro: Create a codespace to get started with developing your project inside a dedicated cloud environment. You can use your codespace in the browser or in a choice of code editors.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -24,3 +24,4 @@ children:
|
|||
- /using-github-codespaces-in-your-jetbrains-ide
|
||||
- /using-github-codespaces-with-github-cli
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Opening an existing codespace
|
||||
intro: 'You can reopen a codespace that you have closed or stopped and return to your work.'
|
||||
intro: You can reopen a codespace that you have closed or stopped and return to your work.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -120,4 +120,4 @@ For more information, see [`gh codespace code`](https://cli.github.com/manual/gh
|
|||
|
||||
{% data reusables.codespaces.opening-codespace-in-jetbrains %}
|
||||
|
||||
{% endjetbrains %}
|
||||
{% endjetbrains %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Stopping and starting a codespace
|
||||
intro: 'You can stop and start your codespace to save resources and to pause work.'
|
||||
intro: You can stop and start your codespace to save resources and to pause work.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -104,4 +104,4 @@ You can use the [Insiders Build of {% data variables.product.prodname_vscode_sho
|
|||
## Further reading
|
||||
|
||||
- "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)"
|
||||
- "[Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)"
|
||||
- "[Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)"
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Using GitHub Codespaces in your JetBrains IDE
|
||||
shortTitle: JetBrains IDEs
|
||||
intro: 'You can use the JetBrains Gateway to connect to your codespace and work in your favorite JetBrains IDE.'
|
||||
intro: You can use the JetBrains Gateway to connect to your codespace and work in your favorite JetBrains IDE.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Working collaboratively in a codespace
|
||||
shortTitle: Work collaboratively
|
||||
intro: You can work collaboratively with other people in a codespace by using {% data variables.product.prodname_vs %} Live Share.
|
||||
intro: 'You can work collaboratively with other people in a codespace by using {% data variables.product.prodname_vs %} Live Share.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -61,4 +61,4 @@ The idle timeout, which automatically stops a codespace after a period of inacti
|
|||
|
||||
## Working collaboratively in someone else's codespace
|
||||
|
||||
If you want to work with someone within a codespace they've created, ask them to set up a Live Share session and send you a link, as described above.
|
||||
If you want to work with someone within a codespace they've created, ask them to set up a Live Share session and send you a link, as described above.
|
||||
|
|
|
|||
|
|
@ -12,3 +12,4 @@ children:
|
|||
- /the-codespace-lifecycle
|
||||
- /deep-dive
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -60,3 +60,4 @@ includeGuides:
|
|||
- /codespaces/codespaces-reference/disaster-recovery-for-codespaces
|
||||
- /codespaces/codespaces-reference/security-in-codespaces
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -54,3 +54,4 @@ children:
|
|||
- /the-githubdev-web-based-editor
|
||||
- /guides
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: Enabling GitHub Codespaces for your organization
|
||||
shortTitle: 'Enable {% data variables.product.prodname_codespaces %}'
|
||||
intro: "You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization's expense."
|
||||
permissions: "To alter an organization's billing settings, you must be an organization owner."
|
||||
intro: 'You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization''s expense.'
|
||||
permissions: 'To alter an organization''s billing settings, you must be an organization owner.'
|
||||
redirect_from:
|
||||
- /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
|
||||
- /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Listing the codespaces in your organization
|
||||
shortTitle: List organization codespaces
|
||||
intro: 'You can list all of the currently active or stopped codespaces for your organization.'
|
||||
intro: You can list all of the currently active or stopped codespaces for your organization.
|
||||
permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
|
|||
|
|
@ -36,4 +36,4 @@ After you enable GPG verification, {% data variables.product.company_short %} wi
|
|||
|
||||
|
||||
|
||||
Once you have enabled GPG verification for {% data variables.product.prodname_github_codespaces %}, all commits are signed by default in your codespaces.
|
||||
Once you have enabled GPG verification for {% data variables.product.prodname_github_codespaces %}, all commits are signed by default in your codespaces.
|
||||
|
|
|
|||
|
|
@ -26,4 +26,4 @@ The security log includes details on what action occurred and when you performed
|
|||
## Further reading
|
||||
|
||||
- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
|
||||
- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)"
|
||||
- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)"
|
||||
|
|
|
|||
|
|
@ -15,3 +15,4 @@ children:
|
|||
- /setting-up-your-java-project-for-codespaces
|
||||
- /setting-up-your-python-project-for-codespaces
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Adding features to a devcontainer.json file
|
||||
shortTitle: Adding features
|
||||
intro: With features, you can quickly add tools, runtimes, or libraries to your dev container configuration.
|
||||
intro: 'With features, you can quickly add tools, runtimes, or libraries to your dev container configuration.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
|
@ -78,4 +78,4 @@ To add features in {% data variables.product.prodname_vscode_shortname %} while
|
|||
|
||||
|
||||
|
||||
{% endvscode %}
|
||||
{% endvscode %}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Configuring dev containers
|
||||
allowTitleToDifferFromFilename: true
|
||||
intro: 'You can customize the dev container configuration for your repository.'
|
||||
intro: You can customize the dev container configuration for your repository.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
|
@ -10,3 +10,4 @@ children:
|
|||
- /adding-features-to-a-devcontainer-file
|
||||
- /automatically-opening-files-in-the-codespaces-for-a-repository
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -11,3 +11,4 @@ children:
|
|||
- /configuring-dev-containers
|
||||
- /setting-up-your-repository
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -10,3 +10,4 @@ children:
|
|||
- /adding-a-codespaces-badge
|
||||
- /setting-up-a-template-repository-for-github-codespaces
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -83,4 +83,4 @@ The following configuration settings for a React template will open the `app.js`
|
|||
}
|
||||
}
|
||||
```
|
||||
For more information, see "[Automatically opening files in the codespaces for a repository](/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository)" and the [dev containers specification](https://containers.dev/implementors/json_reference/#general-properties) on the Development Containers website.
|
||||
For more information, see "[Automatically opening files in the codespaces for a repository](/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/automatically-opening-files-in-the-codespaces-for-a-repository)" and the [dev containers specification](https://containers.dev/implementors/json_reference/#general-properties) on the Development Containers website.
|
||||
|
|
|
|||
|
|
@ -32,4 +32,4 @@ The following steps describe how to export your changes to a branch or fork. For
|
|||
|
||||
1. From the popover or dialog box, select **Create branch** or **Create fork**.
|
||||
|
||||
The name of the new branch will be the permanent name of your codespace prefixed by the string `codespace-`, for example `codespace-monalisa-ideal-space-engine-vj59xj67jg42xx7`.
|
||||
The name of the new branch will be the permanent name of your codespace prefixed by the string `codespace-`, for example `codespace-monalisa-ideal-space-engine-vj59xj67jg42xx7`.
|
||||
|
|
|
|||
|
|
@ -169,4 +169,4 @@ You can download logs for the remote JetBrains IDE and the local client applicat
|
|||
## Further reading
|
||||
|
||||
- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
|
||||
- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)"
|
||||
- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)"
|
||||
|
|
|
|||
|
|
@ -109,4 +109,4 @@ fi
|
|||
|
||||
## Further reading
|
||||
- "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)"
|
||||
- [`git config`](https://git-scm.com/docs/git-config) in the official Git documentation
|
||||
- [`git config`](https://git-scm.com/docs/git-config) in the official Git documentation
|
||||
|
|
|
|||
|
|
@ -32,4 +32,4 @@ If the configuration from your dotfiles is correctly picked up, but part of the
|
|||
|
||||
## Troubleshooting Settings Sync
|
||||
|
||||
{% data reusables.codespaces.disabling-settings-sync %}
|
||||
{% data reusables.codespaces.disabling-settings-sync %}
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Reporting abuse or spam
|
||||
intro: You can report behavior and content that violates community guidelines and terms.
|
||||
permissions: Owners, collaborators, prior contributors, and people with write access can report issues, pull requests, and comments on issues, pull requests, and commits. Anyone can report apps in {% data variables.product.prodname_marketplace %}.
|
||||
permissions: 'Owners, collaborators, prior contributors, and people with write access can report issues, pull requests, and comments on issues, pull requests, and commits. Anyone can report apps in {% data variables.product.prodname_marketplace %}.'
|
||||
redirect_from:
|
||||
- /articles/reporting-abuse-or-spam
|
||||
- /github/building-a-strong-community/reporting-abuse-or-spam
|
||||
|
|
|
|||
|
|
@ -10,3 +10,4 @@ children:
|
|||
- /about-github-copilot
|
||||
- /about-github-copilot-for-business
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -12,3 +12,4 @@ children:
|
|||
- /troubleshooting-github-copilot-in-neovim
|
||||
- /troubleshooting-certificate-errors-for-github-copilot
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Troubleshooting certificate errors for GitHub Copilot
|
||||
intro: 'Troubleshooting help for certificate-related errors.'
|
||||
intro: Troubleshooting help for certificate-related errors.
|
||||
product: '{% data reusables.gated-features.copilot %}'
|
||||
topics:
|
||||
- Copilot
|
||||
|
|
@ -28,4 +28,4 @@ Possible ways to resolve this issue are:
|
|||
|
||||
**Warning:** Ignoring certificate errors is not recommended, since it might cause security issues.
|
||||
|
||||
{% endwarning %}
|
||||
{% endwarning %}
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: Testing your app
|
||||
intro: "GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows."
|
||||
intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.'
|
||||
redirect_from:
|
||||
- /apps/marketplace/testing-apps-apis-and-webhooks
|
||||
- /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
|
||||
- /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
|
||||
- /developers/github-marketplace/testing-your-app
|
||||
versions:
|
||||
fpt: "*"
|
||||
ghec: "*"
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Marketplace
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: Receiving webhooks with the GitHub CLI
|
||||
intro: 'You can use the {% data variables.product.prodname_cli %} to test webhooks in your development environment without the complexity of port forwarding or third-party tools.'
|
||||
versions:
|
||||
feature: 'cli-webhook-forwarding'
|
||||
feature: cli-webhook-forwarding
|
||||
topics:
|
||||
- Webhooks
|
||||
shortTitle: Receiving webhooks with the GitHub CLI
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Webhook events and payloads
|
||||
intro: 'Learn about when each webhook event occurs and what the payload contains.'
|
||||
intro: Learn about when each webhook event occurs and what the payload contains.
|
||||
product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
|
||||
redirect_from:
|
||||
- /early-access/integrations/webhooks
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Creating discussion category forms
|
||||
shortTitle: Create discussion category forms
|
||||
intro: 'You can customize the templates that are available for community members to use when they open new discussions in your repository.'
|
||||
intro: You can customize the templates that are available for community members to use when they open new discussions in your repository.
|
||||
versions:
|
||||
feature: discussion-category-forms
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Syntax for discussion category forms
|
||||
shortTitle: Syntax for discussion category forms
|
||||
intro: 'You can use YAML syntax to define the fields in your discussion category forms.'
|
||||
intro: You can use YAML syntax to define the fields in your discussion category forms.
|
||||
versions:
|
||||
feature: discussion-category-forms
|
||||
---
|
||||
|
|
|
|||
|
|
@ -31,3 +31,4 @@ children:
|
|||
- /manage-coursework-with-github-classroom
|
||||
- /guides
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -63,3 +63,4 @@ children:
|
|||
- /customizing-your-github-workflow
|
||||
- /privacy-on-github
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ If you don't know whether an organization uses {% data variables.product.prodnam
|
|||
|
||||
### {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
If you access {% data variables.product.prodname_dotcom %} at a URL other than https://github.com, `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_server %}. For example, you may access {% data variables.product.prodname_ghe_server %} at `https://github.YOUR-COMPANY-NAME.com`. Your administrators may choose a URL that doesn't include the word "{% data variables.product.company_short %}."
|
||||
If you access {% data variables.product.prodname_dotcom %} at a URL other than https://github.com, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_server %}. For example, you may access {% data variables.product.prodname_ghe_server %} at `https://github.YOUR-COMPANY-NAME.com`. Your administrators may choose a URL that doesn't include the word "{% data variables.product.company_short %}."
|
||||
|
||||
In a wide browser window, the word "Enterprise" immediately follows the {% data variables.product.company_short %} logo on the left side of the header.
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ You can view the version of {% data variables.product.prodname_ghe_server %} tha
|
|||
|
||||
### {% data variables.product.prodname_ghe_managed %}
|
||||
|
||||
If you access {% data variables.product.prodname_dotcom %} at `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_managed %}.
|
||||
If you access {% data variables.product.prodname_dotcom %} at `https://*.ghe.com` or `https://*.github.us`, you're using {% data variables.product.prodname_ghe_managed %}.
|
||||
|
||||
In a wide browser window, the words "{% data variables.product.prodname_ghe_managed %}" immediately follow the {% data variables.product.company_short %} logo in the header.
|
||||
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ In addition to the features available with {% data variables.product.prodname_fr
|
|||
|
||||
## {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% data variables.product.prodname_enterprise %} includes two deployment options: {% data variables.product.prodname_ghe_cloud %}, which is cloud-hosted and part of {% data variables.product.prodname_dotcom_the_website %}, and {% data variables.product.prodname_ghe_server %}, which is self-hosted. For more information, see "[About {% data variables.product.prodname_dotcom %} for enterprises]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-github-for-enterprises){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
{% data variables.product.prodname_enterprise %} includes two deployment options: {% data variables.product.prodname_ghe_cloud %}, which is cloud-hosted and part of {% data variables.product.prodname_dotcom_the_website %}, and {% data variables.product.prodname_ghe_server %}, which is self-hosted.{% ifversion not ghae %} For more information, see "[About {% data variables.product.prodname_dotcom %} for enterprises]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-github-for-enterprises){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
|
||||
In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes:
|
||||
|
||||
|
|
|
|||
|
|
@ -34,3 +34,4 @@ changelog:
|
|||
layout: product-landing
|
||||
beta_product: false
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -150,3 +150,4 @@ externalProducts:
|
|||
href: 'https://docs.npmjs.com/'
|
||||
external: true
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -74,3 +74,4 @@ redirect_from:
|
|||
- /linking-a-pull-request-to-an-issue
|
||||
- /about-duplicate-issues-and-pull-requests
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
title: Adding items automatically
|
||||
intro: "You can configure your project to automatically add items from a repository that match a filter."
|
||||
intro: You can configure your project to automatically add items from a repository that match a filter.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2-auto-add
|
||||
type: tutorial
|
||||
product: "The auto-add workflow is available as a beta release for projects owned by organizations using {% data variables.product.prodname_ghe_cloud %}."
|
||||
product: 'The auto-add workflow is available as a beta release for projects owned by organizations using {% data variables.product.prodname_ghe_cloud %}.'
|
||||
topics:
|
||||
- Projects
|
||||
---
|
||||
|
|
|
|||
|
|
@ -15,3 +15,4 @@ children:
|
|||
- /archiving-items-automatically
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 'Copying an existing {% data variables.projects.project_v2 %}'
|
||||
shortTitle: 'Copying a project'
|
||||
shortTitle: Copying a project
|
||||
intro: You can use an existing project as a template by copying it.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
|
|
|
|||
|
|
@ -13,3 +13,4 @@ children:
|
|||
- /migrating-from-projects-classic
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче