Repository navigation
Qualify GHES Copilot endpoint guidance - #76896
Conversation
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
|
✅ Test Quality Sentinel completed test quality analysis. Test Quality SentinelOutcome: The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible. Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.
|
There was a problem hiding this comment.
🟢 Approval recommended
The documentation now clearly frames the GHES endpoint as conditional routing guidance and links the required prerequisites, with no active review issues identified.
No open issues 🎉
What changed in this PR
Clarifies that the GHES Copilot endpoint is conditional routing guidance rather than a GHES support commitment, while linking to the required licensing, policy, and firewall prerequisites.
Changes:
- Qualifies the GHES
api-targetexample based on account and deployment availability. - States that the example does not establish GHES support.
- Adds a direct link to the GHES Copilot prerequisites.
| File | Description |
|---|---|
| docs/src/content/docs/reference/engines.md | Qualifies the GHES Copilot endpoint example and links to the relevant prerequisites. |
Review effort: Lite (auto)
|
🎉 This pull request is included in a new release. Release: |
The Engines reference described a GHES Copilot endpoint without clarifying that availability is deployment-dependent. This could be read as a GHES support commitment, despite the licensing and firewall prerequisites documented elsewhere.