Skip to content

Commit 82acfd9

Browse files
authored
Add GHES/enterprise compatibility warning to Steps 0 and 5 (#187)
1 parent 88af3dd commit 82acfd9

2 files changed

Lines changed: 18 additions & 3 deletions

File tree

‎workshop/00-welcome.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@
1919
| Actions user | ~1.5 hours | ~75 minutes |
2020
| Advanced | ~45 minutes | ~45 minutes |
2121

22+
> [!NOTE]
23+
> **Enterprise users:** Agentic workflows require **github.com** or **GitHub Enterprise Cloud (GHEC)**. GHES is not supported by default — see [Step 5](05-agentic-workflows-intro.md#platform-compatibility) for details and workarounds.
2224
## Why this matters in 60 seconds
2325

2426
**In about 2 hours, you'll have an AI-powered daily repo health report running automatically in GitHub** — the kind of workflow a teammate or evaluator can judge in under a minute.

‎workshop/05-agentic-workflows-intro.md‎

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,24 @@ Use this as a one-page reference for the shift from classic workflows to agentic
5454
- Triggers, permissions, and repository context still matter
5555
- You still version workflows in git and review them like code
5656

57-
> [!NOTE]
58-
> **Enterprise users:** Agentic workflows are supported on **GitHub Enterprise Cloud (GHEC)** and **GitHub Enterprise Server (GHES) 3.14+**. If your organization uses a proxy or mandates self-hosted runners, see the [GitHub Actions self-hosted runners documentation](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners) for setup requirements before continuing. The `gh-aw` CLI and all workshop steps work identically once your runner environment is configured.
59-
6057
The same authoring and review workflow applies everywhere — only the runner configuration differs.
6158

59+
## Platform Compatibility
60+
61+
> [!WARNING]
62+
> **GHES (GitHub Enterprise Server) users:** Agentic workflows are **not supported by default** on GHES. Support varies by version and organization configuration. If you are on a GHES instance and agentic workflows are not enabled, you will encounter 404 errors or permission failures at Steps 6–8 with no clear explanation.
63+
>
64+
> **Recommended options for GHES users:**
65+
> - Follow along in read-only mode to learn the concepts — you can still complete all non-execution steps.
66+
> - Request a **github.com** account (free tier is sufficient) to run the hands-on portions of the workshop.
67+
> - Ask your GitHub Enterprise administrator whether agentic workflows have been enabled for your organization.
68+
69+
| GitHub deployment | Agentic workflows supported? |
70+
|---|---|
71+
| **github.com** (free/Team/Enterprise) | ✅ Fully supported |
72+
| **GitHub Enterprise Cloud (GHEC)** | ✅ Fully supported |
73+
| **GitHub Enterprise Server (GHES)** | ⚠️ Not supported by default — varies by version and org configuration |
74+
6275
> [!IMPORTANT]
6376
> In this workshop, learn to iterate on agentic workflows by asking Copilot (or another capable agent) to use the `agentic-workflows` skill. Reading the workflow directly helps you understand it, but editing and debugging agentic workflows by hand is usually less effective. **Agents edit agents.**
6477

0 commit comments

Comments
 (0)