-
Notifications
You must be signed in to change notification settings - Fork 141
Feat: Add GitHub Copilot Quickstart Guide - WIP #2231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Added GitHub Copilot and related extensions to the devcontainer configuration. - Created a new documentation page for using AVM with GitHub Copilot. - Included setup instructions and productivity tips for AVM module development.
- Revised introduction to clarify how GitHub Copilot enhances productivity with Azure Verified Modules (AVM). - Expanded list of areas where GitHub Copilot can assist in Infrastructure as Code (IaC) development.
- Updated sections to include detailed usage scenarios for GitHub Copilot with AVM. - Added new topics on configuring MCP servers, adding prompt files, and modes. - Improved clarity and structure for better user guidance.
- Added GitHub Copilot Chat and GitHub Copilot for Azure extensions to the devcontainer configuration. - Created a new MCP configuration file for GitHub Copilot. - Updated documentation to reflect changes in setting up the environment for GitHub Copilot.
- Reformatted JSON structure in mcp.json for consistency. - Updated GitHub Copilot usage documentation for clarity.
- Added `github-copilot-prompt-file-install-location.png` to illustrate the installation location for GitHub Copilot prompts. - Added `github-copilot-prompt-file-install-name.png` to demonstrate the naming conventions for GitHub Copilot prompt files.
- Renamed section from "Configuring MCP Servers" to "Adding MCP Servers" - Added details on configuring MCP servers in Visual Studio Code - Included links to relevant Visual Studio Code documentation - Added a new section for "Instruction Files" with a note on availability
- Introduced custom chat modes for Bicep and Terraform in GitHub Copilot. - Added installation instructions and links to the Awesome-Copilot repository. - Enhanced documentation for using custom chat modes in Visual Studio Code.
| @@ -0,0 +1,186 @@ | |||
| --- | |||
| draft: true | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can remove this as im sure we'll forget before merging and then it wont appear 👍
| <img src="{{% siteparam base %}}/images/usage/gh-copilot/github-copilot-chat-mode-install-confirm.png" alt="Confirm installation of Prompt File into VS Code" style="max-width:800px;" /> | ||
|
|
||
| 1. Select whether to install the custom chat mode into this workspace (`.github/chatmode/`) or into your global user account, making it available to every workspace you work on. | ||
|
|
||
| <img src="{{% siteparam base %}}/images/usage/quickstart/github-copilot/github-copilot-chat-mode-install-location.png" alt="Select scope of Prompt File" style="max-width:800px;" /> | ||
|
|
||
| 1. You can choose a name for the custom chat mode, or leave it as the default name. | ||
|
|
||
| <img src="{{% siteparam base %}}/images/usage/quickstart/github-copilot/github-copilot-chat-mode-install-name.png" alt="Select scope of Prompt File" style="max-width:800px;" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing these images in the branch?
|
|
||
| ### Instruction Files | ||
|
|
||
| TBC - currently no AVM specific instruction files are available (there are TF and Bicep ones though) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Links to them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually what about the one in the BRM repo? in the other PR you have
| ### Creating Documentation for Your AVM IaC | ||
|
|
||
| GitHub Copilot can also help you create documentation for your AVM IaC. For example, you can start by writing a comment or a function name, and GitHub Copilot will suggest documentation based on the context of your code. This can help you create consistent and comprehensive documentation for your AVM modules. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably not one to add here as we have scripts and tools for both TF and Bicep to autogenerate this that is checked with our CI
|
|
||
| If you need to refactor existing AVM IaC to use different technologies or architectures, GitHub Copilot can help. For example, if you're moving to a zero trust architecture, you can start by modifying the existing code and GitHub Copilot will suggest changes based on the context of your modifications. | ||
|
|
||
| ### Updating Existing AVM Modules to Use the Latest Version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a similar one for API versions, especially as we are promoting the use of azapi provider in TF as well now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feel like we need to split the docs/scenarios in to separate sections for
- AVM module owners
- AVM module consumers
As they both will use very differently
Overview/Summary
Adds GitHub Copilot Quickstart Guide.
This PR fixes/adds/changes/removes
Using AVM with GitHub Copilotdocument (still in draft)Breaking Changes
N/A
As part of this Pull Request I have
mainbranch