jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-08 21:02:10 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #27596 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2023-08-21 03:32:11 -05:00
committed by GitHub
parent 4f6f46542e 37bd195133
commit 71509f2ee5
16 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md
View File

@@ -22,7 +22,7 @@ However, because {% data variables.product.prodname_github_codespaces %} incurs
Automatic deletion happens irrespective of whether a codespace contains unpushed changes. To prevent automatic deletion of a codespace, just open the codespace again. The retention period is reset every time you connect to a codespace, and the retention countdown restarts when the codespace is stopped.
If a repository belongs to an organization, the organization admin may have set a retention period for the whole organization. If this period is less than the default retention period in your personal settings then the organization retention period will apply to codespaces you create for this repository. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
If a repository belongs to an organization, the organization owner may have set a retention period for the whole organization. If this period is less than the default retention period in your personal settings then the organization retention period will apply to codespaces you create for this repository. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
Each codespace has its own retention period. You may, therefore, have codespaces with different retention periods. For example, if:
- You created a codespace, changed your default retention period, then created another codespace.

2
content/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md
View File

@@ -30,7 +30,7 @@ As an organization owner, you can add a policy to restrict which images can be u
If the image specified in the dev container configuration does not match one of the allowed images, the following message is displayed when someone tries to create a codespace for the repository:
> Codespace could not be created: Base image 'DETAILS FROM DEV CONTAINER CONFIGURATION' is not allowed based on an organization policy set by your organization administrator.
> Codespace could not be created: Base image 'DETAILS FROM DEV CONTAINER CONFIGURATION' is not allowed based on an organization policy set by your organization owner.
{% note %}

4
content/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization.md
View File

@@ -15,9 +15,9 @@ shortTitle: Organization settings
{% data reusables.copilot.about-copilot %}
{% ifversion ghec %}To configure {% data variables.product.prodname_copilot %} use in your organization, the organization must be owned by a {% data variables.product.prodname_ghe_cloud %} account, and an enterprise admin must first enable {% data variables.product.prodname_copilot_business_short %} for your organization. Organization admins will then be able to manage seat assignment within the organization.
{% ifversion ghec %}To configure {% data variables.product.prodname_copilot %} use in your organization, the organization must be owned by a {% data variables.product.prodname_ghe_cloud %} account, and an enterprise admin must first enable {% data variables.product.prodname_copilot_business_short %} for your organization. Organization owners will then be able to manage seat assignment within the organization.
Depending on the policy settings configured at the enterprise level, an organization admin may also be able to determine whether to allow or block {% data variables.product.prodname_copilot %} suggestions that match public code. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-copilot-in-your-enterprise)."{% endif %}
Depending on the policy settings configured at the enterprise level, an organization owner may also be able to determine whether to allow or block {% data variables.product.prodname_copilot %} suggestions that match public code. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-copilot-in-your-enterprise)."{% endif %}
## Configuring access to {% data variables.product.prodname_copilot %} in your organization

4
content/copilot/overview-of-github-copilot/enabling-and-setting-up-github-copilot-for-business.md
View File

@@ -26,7 +26,7 @@ To use {% data variables.product.prodname_copilot_for_business %}, you need to s
Your enterprise owner can enable {% data variables.product.prodname_copilot_business_short %} for the organizations in the enterprise by first establishing the policy and then assigning users. To enforce a policy to manage the use of {% data variables.product.prodname_copilot_business_short %}, follow the steps in "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-copilot-in-your-enterprise#enforcing-a-policy-to-manage-the-use-of-github-copilot-for-business-in-your-enterprise)." If you need additional help with policy configuration or user assignment for {% data variables.product.prodname_copilot_business_short %}, you can contact {% data variables.contact.contact_enterprise_sales %}.
{% data variables.product.prodname_copilot %} includes a filter which detects code suggestions that match public code on {% data variables.product.prodname_dotcom %}. Your enterprise owner can choose whether to enable or disable the filter at the enterprise-level, or allow organization administrators to decide at the organization-level. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-copilot-in-your-enterprise#enforcing-a-policy-to-manage-the-use-of-github-copilot-suggestions-that-match-public-code-in-your-enterprise)."{% endif %}
{% data variables.product.prodname_copilot %} includes a filter which detects code suggestions that match public code on {% data variables.product.prodname_dotcom %}. Your enterprise owner can choose whether to enable or disable the filter at the enterprise-level, or allow organization owners to decide at the organization-level. For more information, see "[AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-copilot-in-your-enterprise#enforcing-a-policy-to-manage-the-use-of-github-copilot-suggestions-that-match-public-code-in-your-enterprise)."{% endif %}
## Configuring {% data variables.product.prodname_copilot %} settings in your organization
@@ -37,7 +37,7 @@ Your enterprise owner can enable {% data variables.product.prodname_copilot_busi
{% endnote %}
Once an enterprise owner has enabled {% data variables.product.prodname_copilot_business_short %} for an organization, organization administrators and members with admin permissions can configure {% data variables.product.prodname_copilot %} access for their organization. Depending on the policy settings configured at the enterprise-level, an organization administrator may also be able to determine whether to allow or block {% data variables.product.prodname_copilot %} suggestions that match public code.{% endif %}{% ifversion fpt %}After setting up a {% data variables.product.prodname_copilot_business_short %} subscription for your organization, you can configure {% data variables.product.prodname_copilot %} settings in your organization. This includes granting and revoking access to individuals and teams, and determining whether to block suggestions that match public code.{% endif %} For more information, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization)."
Once an enterprise owner has enabled {% data variables.product.prodname_copilot_business_short %} for an organization, organization owners and members with admin permissions can configure {% data variables.product.prodname_copilot %} access for their organization. Depending on the policy settings configured at the enterprise-level, an organization owner may also be able to determine whether to allow or block {% data variables.product.prodname_copilot %} suggestions that match public code.{% endif %}{% ifversion fpt %}After setting up a {% data variables.product.prodname_copilot_business_short %} subscription for your organization, you can configure {% data variables.product.prodname_copilot %} settings in your organization. This includes granting and revoking access to individuals and teams, and determining whether to block suggestions that match public code.{% endif %} For more information, see "[AUTOTITLE](/copilot/configuring-github-copilot/configuring-github-copilot-settings-in-your-organization)."
## Assigning {% data variables.product.prodname_copilot %} seats

2
content/rest/codespaces/organizations.md
View File

@@ -15,7 +15,7 @@ autogenerated: rest
You can manage {% data variables.product.prodname_codespaces %} billed to your
organization. These endpoints are available for authenticated
organization admins and {% data variables.product.prodname_oauth_apps %}, but not GitHub Apps. For more information,
organization owners and {% data variables.product.prodname_oauth_apps %}, but not GitHub Apps. For more information,
see "[AUTOTITLE](/codespaces)."
<!-- Content after this section is automatically generated -->

2
data/release-notes/enterprise-server/3-8/3.yml
View File

@@ -51,3 +51,5 @@ sections:
# https://github.com/github/driftwood/issues/2746
- |
On an instance with audit log streaming enabled, the `driftwood` service does not start, preventing the normal operation of audit log streaming. [Updated: 2023-06-06]
- |
{% data reusables.release-notes.mermaid-rendering-known-issue %} [Updated: 2023-08-18]

2
data/release-notes/enterprise-server/3-8/4.yml
View File

@@ -36,4 +36,4 @@ sections:
- |
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}

3
data/release-notes/enterprise-server/3-8/5.yml
View File

@@ -13,7 +13,6 @@ sections:
- After an enterprise owner set a permanent rate limit for a users GitHub App at `http(s)://HOSTNAME/stafftools/users/USERNAME/installations`, the instance did not respect the rate limit.
- On an instance with multiple nodes, when using the `spokesctl` command-line utility to manage repositories with replicas that failed to fully create, the utility would spuriously attempt to repair healthy replicas.
- On an instance with a GitHub Advanced Security license and code scanning enabled, code scanning could not process some SARIF files produced by newer versions of CodeQL.
- On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI displayed an "Unable to render rich display" error and failed to render.
changes:
- If a configuration runs fails due to Elasticsearch errors, `ghe-config-apply` displays a more actionable error message.
known_issues:
@@ -38,6 +37,6 @@ sections:
- |
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}
- |
Organization owners cannot register a new SSH certificate authorities (CAs) due to an erroneous suggestion to start a trial. Organization SSH CAs configured before an upgrade to an affected version are still usable after the upgrade. Enterprise owners can can still register SSH CAs for all organizations.

2
data/release-notes/enterprise-server/3-8/6.yml
View File

@@ -95,6 +95,6 @@ sections:
- |
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}
- |
{% data reusables.release-notes.enterprise-backup-utils-encryption-keys %}

2
data/release-notes/enterprise-server/3-8/7.yml
View File

@@ -16,7 +16,7 @@ sections:
- |
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}
- |
{% data reusables.release-notes.enterprise-backup-utils-encryption-keys %}
changes:

2
data/release-notes/enterprise-server/3-8/8.yml
View File

@@ -45,4 +45,4 @@ sections:
- |
When running `ghe-config-apply`, the process may stall with the message `Deployment is running pending automatic promotion`.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}

2
data/release-notes/enterprise-server/3-9/0.yml
View File

@@ -416,6 +416,8 @@ sections:
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
- |
If the root site administrator is locked out of the Management Console after failed login attempts, the account will not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
- |
{% data reusables.release-notes.mermaid-rendering-known-issue %} [Updated: 2023-08-18]
deprecations:
# https://github.com/github/releases/issues/2826

5
data/release-notes/enterprise-server/3-9/1.yml
View File

@@ -85,8 +85,6 @@ sections:
On an instance with a GitHub Advanced Security license that was also configured for a timezone greater than UTC, the list of secret scanning alerts displayed a "Loading secrets failed" error if a user sorted secrets by date in descending order.
- |
Code Scanning workflow runs now only request the `code-scanning` label so that they can be used with runner scale sets.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI displayed an "Unable to render rich display" error and failed to render.
changes:
- |
On an instance in a cluster configuration, the `ghe-cluster-config-check` command-line utility will return an affirmative message when no warnings or errors are detected. The affirmative message is "Configuration validation complete. No errors found."
@@ -135,4 +133,5 @@ sections:
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
- |
If the root site administrator is locked out of the Management Console after failed login attempts, the account will not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
- |
{% data reusables.release-notes.mermaid-rendering-known-issue %} [Updated: 2023-08-18]

2
data/release-notes/enterprise-server/3-9/2.yml
View File

@@ -44,6 +44,8 @@ sections:
During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
- |
If the root site administrator is locked out of the Management Console after failed login attempts, the account will not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
- |
{% data reusables.release-notes.mermaid-rendering-known-issue %} [Updated: 2023-08-18]
changes:
- |
Added a pre-upgrade check to validate the GHES version and MySQL configuration before allowing an upgrade to 3.9.

2
data/release-notes/enterprise-server/3-9/3.yml
View File

@@ -48,7 +48,7 @@ sections:
- |
The `mbind: Operation not permitted` error in the `/var/log/mysql/mysql.err` file can be ignored. MySQL 8 does not gracefully handle when the `CAP_SYS_NICE` capability isn't required, and outputs an error instead of a warning.
- |
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.
{% data reusables.release-notes.mermaid-rendering-known-issue %}
- |
When enabling CodeQL via default setup [at scale](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-at-scale), some checks related to GitHub Actions are omitted, potentially preventing the process from completing.

1
data/reusables/release-notes/mermaid-rendering-known-issue.md Normal file
View File

@@ -0,0 +1 @@
On an instance with subdomain isolation disabled, Mermaid diagrams in the web UI display an "Unable to render rich display" error and fail to render.