How microsoft/vscode-copilot-release works
Project type and purpose
• This is a “feedback‐collection” repository for two VS Code extensions (GitHub Copilot and GitHub Copilot Chat). It does not ship production code of the extensions themselves but provides issue templates, docs, and metadata so that users can file bugs or feature requests.
File structure
• Top‐level:
• .github/ISSUE_TEMPLATE – predefined issue templates for bugs and feature requests (chat vs completions)
• .github/commands.json – custom GitHub CLI commands or bot labels
• docs/ – static documentation on repo scope and usage
• images/ – supporting graphics referenced in docs or the README
• README.md, CODE_OF_CONDUCT.md, SECURITY.md, LICENSE* – governance and getting-started documentation
• No “src” or “backend” folders – this is a documentation/meta‐repo, so its “components” are templates and GitHub workflows rather than code modules.
README for additional insights
• Purpose: funnel all VS Code Copilot-related UX feedback into one place
• User flows: reporting a bug or requesting a feature, choosing the right template, upvoting existing issues, triage by maintainers
Detail without over-splitting
• Clearly call out each template (bug vs feature; chat vs completions)
• Docs directory feeding into onboarding or “where to file” guidance