Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,73 @@ If you're using a dedicated block device as your backup target, you need to init
* Sets it to mount automatically at `/data/backup` on boot.{% ifversion ghes > 3.19 %}
* If in a clustered environment, configures the node in `cluster.conf` with the `backup-server` role.{% endif %}

#### Increasing the data partition size

1. Resize the existing backup disk volume mounted at `/data/backup` using your virtualization platform's tools.
1. Connect via SSH as the `admin` user to the node where the backup disk is mounted. See [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh).
1. Put the appliance in maintenance mode. For more information, see [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode).
1. Reboot the appliance to detect the new storage allocation:

```shell
sudo reboot
```

1. Run the `ghe-backup-disk-extend` command to expand the `/data/backup` filesystem:

```shell
ghe-backup-disk-extend
```

1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see [AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode).

> [!WARNING]
> If the `ghe-backup-disk-extend` command (or a prior automatic check) reports: `ghe_backup_data contains a file system with errors`, you must repair the filesystem before retrying the resize. Do not rerun `ghe-backup-disk-extend` until the check completes cleanly. For recovery instructions, see below.


#### Repairing filesystem errors

If the filesystem check fails during `ghe-backup-disk-extend`, follow these steps to repair it.

1. Ensure the appliance is in maintenance mode and no background jobs are running:

```shell copy
ghe-maintenance -s
ghe-resque-info
```

1. Stop and activate the user volume, then run a forced filesystem check (auto‑answer yes):

```shell copy
sudo systemctl stop ghe-backup-disk
VGNAME=$(sudo lvs --noheadings -o vg_name | grep ghe_backup_ | awk '{ print $1 }')
sudo vgchange -ay "$VGNAME"
sudo vgscan --mknodes
sudo fsck -fy /dev/mapper/${VGNAME}-ghe_backup_data
```

1. Retry the resize:

```shell copy
ghe-backup-disk-extend
```

1. Remount and verify new size:

```shell copy
sudo systemctl start ghe-backup-disk
df -h /data/backup
```

1. Reboot and verify the new size.



1. After the appliance restarts, reconnect via SSH to the node on which the backup disk is mounted, then verify the new size:

```shell copy
df -h /data/backup
```

#### Detach a backup disk

> [!WARNING]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,6 @@ The following features are currently unavailable on {% data variables.enterprise
| Maven and Gradle support for {% data variables.product.prodname_registry %} | Currently unavailable. | [AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) |
| {% data variables.product.prodname_marketplace %} | {% data variables.product.prodname_marketplace %}, as a means of searching for, purchasing, and directly installing apps and actions, is unavailable. Ecosystem apps and actions can still be discovered and installed from their source, but they may require modification to work on {% data variables.enterprise.data_residency_site %}. | [{% data variables.product.prodname_actions %} workflows from {% data variables.product.prodname_marketplace %}](#github-actions-workflows-from-github-marketplace) |
| Some features currently in {% data variables.release-phases.public_preview %} or {% data variables.release-phases.private_preview %} | Certain features that are in a preview phase on {% data variables.product.prodname_dotcom_the_website %} may not be available on {% data variables.enterprise.data_residency_site %} until GA. | |
| Streaming audit logs to Amazon S3 with OpenID Connect (OIDC) | Currently unavailable. | [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise) |

## Permanently unavailable features

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -152,8 +152,8 @@ From {% data variables.product.prodname_dotcom %}:

#### Setting up streaming to S3 with OpenID Connect

> [!NOTE]
> Audit log streaming to S3 with OpenID Connect for {% data variables.enterprise.data_residency %} is currently unavailable. See [AUTOTITLE](/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency#currently-unavailable-features).
> [!WARNING]
> Streaming exports audit log data to the AWS bucket and region you choose, which can be outside your enterprise's data residency region. Review the destination against your data residency and compliance requirements before enabling streaming.

From AWS:

Expand All @@ -179,18 +179,27 @@ From AWS:
}
```

For {% data variables.enterprise.data_residency %}, replace the `sub` condition with the following, replacing `SUBDOMAIN` with your enterprise's subdomain:

```json
"oidc-configuration.audit-log.githubusercontent.com:sub": "https://SUBDOMAIN.ghe.com"
```

The `SUBDOMAIN` value is case-sensitive. Use the lowercase subdomain exactly as it appears in your enterprise's URL, not its display name. Keep the `aud` condition set to `sts.amazonaws.com`.

If your enterprise's subdomain changes or the enterprise is deleted, remove the old subject from your AWS role trust policies. Creating a new trust policy does not revoke an old one.

* Make note of the Amazon Resource Name (ARN) of the created role.

From {% data variables.product.prodname_dotcom %}:
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
{% data reusables.audit_log.streaming-choose-s3 %}
1. Under "Authentication", click **OpenID Connect**.
1. Configure the stream settings.
1. Configure the stream settings.{% ifversion ghec %}

{% ifversion ghec %}
- Under "Region", select the bucket's region. For example, `us-east-1`; an option for Auto Discovery is also available.{% endif %}
- Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
- Under "ARN Role" type the ARN role you noted earlier. For example, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
* Under "Region", select the bucket's region. For example, `us-east-1`. An option for Auto Discovery is also available. If you use Auto Discovery, verify the destination bucket's region and role ARN before enabling streaming.{% endif %}
* Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
* Under "ARN Role" type the ARN role you noted earlier. For example, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
{% data reusables.audit_log.streaming-check-s3-endpoint %}
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Answering approval prompts keeps you in control, but it can slow you down, espec
{% data variables.copilot.assisted_permissions_caps %} is a middle ground between manual approval and granting broad permissions with an allow-all option. It uses a large language model to review permission requests and automatically approve actions it judges to be safe in the context of your task. In a standard interactive session, requests that still require approval are put to you.

> [!NOTE]
> {% data variables.copilot.assisted_permissions_caps %} is available in {% data variables.copilot.copilot_cli %}, {% data variables.product.prodname_vscode %}, and the {% data variables.copilot.github_copilot_app %}.
> {% data variables.copilot.assisted_permissions_caps %} is available in {% data variables.copilot.copilot_cli %}, {% data variables.product.prodname_vscode %}, and the {% data variables.copilot.github_copilot_app %}. For accurate billing of safety reviews, use {% data variables.copilot.copilot_cli %} version 1.0.104 or later, or the {% data variables.copilot.github_copilot_app %} version 1.1.32 or later. In {% data variables.product.prodname_vscode %}, it's generally available in version 1.143 or later.

## Approval options

Expand Down Expand Up @@ -53,7 +53,13 @@ If a safety review is unavailable or cannot evaluate a request, the request foll
> [!NOTE]
> In autopilot mode and non-interactive runs, requests that still require your approval are denied instead. When the safety review requires approval, its explanation is passed back to {% data variables.product.prodname_copilot_short %} so it can try a different approach. See [AUTOTITLE](/copilot/concepts/agent-capabilities/agent-powered-workflows-and-operations/autopilot).

{% data variables.product.prodname_copilot_short %} selects the model used for the safety review, which can differ from the model you selected for your conversation. If the selected review model is unavailable, the review can use your session's active model instead. If you use your own model provider, the review uses your session's active model.
{% data variables.product.prodname_copilot_short %} selects the model used for the safety review, which can differ from the model you selected for your conversation. By default, the safety review uses a GPT Luna model. If the selected model isn't available to you, {% data variables.product.prodname_copilot_short %} uses another model that has been evaluated for safety reviews. If none of these models is available, the request follows the session's normal permission handling. If you use your own model provider, the review uses your session's active model.

Unless you use your own model provider, each safety review is a separate model request that consumes {% data variables.product.prodname_ai_credits_short %}, in addition to the {% data variables.product.prodname_ai_credits_short %} your task uses. If you use your own model provider, each safety review is a separate request to that provider. With your own model provider, reviews don't consume {% data variables.product.prodname_ai_credits_short %}, but your provider may charge you for those requests. Requests that are already resolved by your permissions or rules don't need a safety review.

Each safety review typically uses about 0.1 {% data variables.product.prodname_ai_credits_short %} or less with {% data variables.copilot.gpt_6_luna %}. Your usage depends on how many requests are reviewed and how much context each review evaluates.

For model rates, see [AUTOTITLE](/copilot/reference/copilot-billing/models-and-pricing).

> [!IMPORTANT]
> {% data variables.copilot.assisted_permissions_caps %} reduces how often you're prompted, but it doesn't remove your responsibility for what {% data variables.product.prodname_copilot_short %} does. The model can make mistakes and approve dangerous or unintended actions. This feature is not a substitute for sandboxing or access restrictions. As with any automatic approval option, you should review the actions {% data variables.product.prodname_copilot_short %} takes, and consider running it in a sandbox or other isolated environment. For more information, see [AUTOTITLE](/copilot/concepts/copilot-surfaces/copilot-cli#risk-mitigation).
Expand Down
2 changes: 2 additions & 0 deletions content/pull-requests/reference/forks.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ Each fork can have its own:

Repository, organization, and enterprise policies can limit whether repositories can be forked and where forks can be created. For private{% ifversion ghec or ghes %} and internal{% endif %} repositories, access to forks also depends on repository visibility, organization membership, and administrator settings.

On {% data variables.product.prodname_dotcom_the_website %}, if you see “You cannot fork this repository at this time” when trying to fork a public repository to your personal account, an account restriction can prevent you from creating a fork, even if you can sign in. The error alone doesn't identify the cause. If you believe your account has been restricted, you can request a review through the [{% data variables.product.github %} Appeal and Reinstatement form](https://support.github.com/contact/reinstatement).

{% ifversion fpt or ghec %}

If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, additional restrictions apply to the repositories you can fork. {% ifversion ghec %}{% data reusables.enterprise-accounts.emu-forks %}{% endif %} See [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/identity-and-access-management/enterprise-managed-users){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
Expand Down
4 changes: 4 additions & 0 deletions data/release-notes/enterprise-server/3-19/0.yml
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,10 @@ sections:
- |
YJIT, Ruby's Just-In-Time (JIT) compiler, is enabled by default. Users may experience faster application performance and improved resource efficiency across their instance. [Updated: 2025-12-17]

bugs:
- |
{% data reusables.release-notes.2026-11-saml-issues-non-org-members-fixed %} [Updated: 2026-11-17]

known_issues:
# INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB
- |
Expand Down
12 changes: 8 additions & 4 deletions data/release-notes/enterprise-server/3-19/15.yml
Original file line number Diff line number Diff line change
@@ -1,16 +1,17 @@
date: '2026-11-10'
intro: |
> [!WARNING]
> The Git security fixes previously listed for this release were incomplete. To receive these fixes, upgrade to {% data variables.product.prodname_ghe_server %} [3.19.16](#3.19.16) or a later patch release of 3.19. [Updated: 2026-11-17]
sections:
security_fixes:
- |
**CRITICAL**: The Ruby Active Storage component was updated to address the file-read and remote code execution vulnerability [CVE-2026-66066](https://www.cve.org/CVERecord?id=CVE-2026-66066).
Packages have been updated to the latest security versions.
- |
**HIGH**: Updated Git to include fixes that address [CVE-2026-105437](https://www.cve.org/CVERecord?id=CVE-2026-105437), [CVE-2026-111760](https://www.cve.org/CVERecord?id=CVE-2026-111760), [CVE-2026-113408](https://www.cve.org/CVERecord?id=CVE-2026-113408), [CVE-2026-114466](https://www.cve.org/CVERecord?id=CVE-2026-114466), [CVE-2026-114467](https://www.cve.org/CVERecord?id=CVE-2026-114467), and [CVE-2026-114469](https://www.cve.org/CVERecord?id=CVE-2026-114469).
**CRITICAL**: The Ruby Active Storage component was updated to address the file-read and remote code execution vulnerability [CVE-2026-66066](https://www.cve.org/CVERecord?id=CVE-2026-66066).
- |
**MODERATE**: The Brotli compression library bundled with the GitHub application was updated to address [CVE-2026-111497](https://www.cve.org/CVERecord?id=CVE-2026-111497).
- |
Security updates have been applied to Go, OpenSSL, and Ubuntu system packages, including SQLite, across targeted main and bundled container images. These updates partially address [CVE-2026-111943](https://www.cve.org/CVERecord?id=CVE-2026-111943), [CVE-2025-15467](https://www.cve.org/CVERecord?id=CVE-2025-15467), and [CVE-2025-6965](https://www.cve.org/CVERecord?id=CVE-2025-6965); remaining components will be updated in a future release.
- |
Packages have been updated to the latest security versions.
known_issues:
- |
When users clone or fetch a repository over SSH with compression enabled, the operation can stall until the connection times out, especially for repositories with many references. To work around this, users can disable SSH compression or use HTTPS. [Updated: 2026-11-13]
Expand Down Expand Up @@ -46,3 +47,6 @@ sections:
The setting to define private registries at the organization level for code scanning is only available if Dependabot is also enabled for the instance.
- |
After a restart, an instance can remain unavailable with "Starting..." displayed in the web interface. To recover, an administrator can connect using administrative SSH and rerun `ghe-config-apply`. This provides temporary recovery but does not prevent the issue from recurring. This issue is resolved in {% data variables.product.prodname_ghe_server %} 3.21.0 and later.
errata:
- |
The security fix note for [CVE-2026-105437](https://www.cve.org/CVERecord?id=CVE-2026-105437), [CVE-2026-111760](https://www.cve.org/CVERecord?id=CVE-2026-111760), [CVE-2026-113408](https://www.cve.org/CVERecord?id=CVE-2026-113408), [CVE-2026-114466](https://www.cve.org/CVERecord?id=CVE-2026-114466), [CVE-2026-114467](https://www.cve.org/CVERecord?id=CVE-2026-114467), and [CVE-2026-114469](https://www.cve.org/CVERecord?id=CVE-2026-114469) has been removed because the Git security fixes were incomplete in this release. These fixes are included in {% data variables.product.prodname_ghe_server %} 3.19.16. [Updated: 2026-11-17]
Loading
Loading