Enterprise Configuration
Enterprise Configuration
Section titled “Enterprise Configuration”This page covers configuration options specific to GitHub Enterprise Server (GHES) and GitHub Enterprise Cloud (GHEC) deployments.
GitHub Enterprise Server (GHES) Compatibility
Section titled “GitHub Enterprise Server (GHES) Compatibility”GHES Compatibility Mode
Section titled “GHES Compatibility Mode”GHES instances running versions that predate @actions/artifact v2.0.0 support cannot use actions/upload-artifact@v4+ or actions/download-artifact@v4+. Attempting to run compiled workflows on these instances produces a GHESNotSupportedError.
gh-aw includes a GHES compatibility mode toggle (aw.json ghes or gh aw compile --ghes) so GHES-targeted repositories can compile with explicit GHES mode enabled. Artifact actions continue using the latest non-v3 pins because v3 artifact actions are deprecated.
Enable via aw.json (recommended)
Section titled “Enable via aw.json (recommended)”Set ghes: true in .github/workflows/aw.json to apply GHES compatibility to every workflow compiled in the repository:
{ "ghes": true}Auto-detection with gh aw init
Section titled “Auto-detection with gh aw init”Running gh aw init inside a GHES repository automatically detects the deployment and writes ghes: true to .github/workflows/aw.json. No manual configuration is required.
Enable via CLI flag
Section titled “Enable via CLI flag”Pass --ghes to gh aw compile for a one-off compilation without modifying aw.json:
gh aw compile --ghes my-workflow.mdGitHub Enterprise Server CLI Setup
Section titled “GitHub Enterprise Server CLI Setup”For gh CLI configuration, host authentication, and GH_HOST setup on GHES, see GitHub Enterprise Server Support in the CLI reference.
Copilot Engine on GHES
Section titled “Copilot Engine on GHES”For Copilot-specific prerequisites, licensing requirements, and firewall configuration on GHES, see Copilot Engine Prerequisites on GHES.