-
Notifications
You must be signed in to change notification settings - Fork 62.5k
Open
Labels
contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamcopilotContent related to GitHub CopilotContent related to GitHub Copilothelp wantedAnyone is welcome to open a pull request to fix this issueAnyone is welcome to open a pull request to fix this issue
Description
Summary
The asking-github-copilot-questions-in-your-ide.md
article is missing Enterprise Server (GHES) version coverage, only showing content for GitHub Enterprise Cloud (GHEC).
Location
- File:
content/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide.md
- Problem: Missing GHES versioning blocks
- Impact: Enterprise Server users cannot access relevant content sections
Current problem
The article contains GHEC-only versioning blocks without corresponding GHES coverage:
Missing GHES blocks:
- Line 32-35: GHEC-only content about GitHub Copilot Chat availability
- Line 89-92: GHEC-only content about organizational policies
Enterprise Server users see incomplete information or missing sections.
Proposed solution
- Add GHES versioning blocks - Include appropriate
{% ifversion ghes %}
blocks for Enterprise Server content - Verify content accuracy - Ensure GHES-specific content reflects actual Enterprise Server capabilities
- Test rendering - Verify the article renders correctly for both GHEC and GHES versions
- Follow versioning patterns - Align with established GitHub Docs versioning standards
Additional context
Reference: Identified during PR #38720 review by @Sharra-writes
Related: Part of broader versioning consistency improvement initiative
Code of Conduct
- I agree to follow this project's Code of Conduct
RUDYWESSY
Metadata
Metadata
Assignees
Labels
contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamcopilotContent related to GitHub CopilotContent related to GitHub Copilothelp wantedAnyone is welcome to open a pull request to fix this issueAnyone is welcome to open a pull request to fix this issue