Skip to content

Conversation

@PlagueHO
Copy link
Member

@PlagueHO PlagueHO commented Jul 25, 2025

Overview/Summary

Adds GitHub Copilot Quickstart Guide.

This PR fixes/adds/changes/removes

  1. Adds Using AVM with GitHub Copilot document (still in draft)

Breaking Changes

N/A

As part of this Pull Request I have

PlagueHO added 2 commits July 26, 2025 11:43
- 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.
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 Maintainers need to triage still label Jul 25, 2025
PlagueHO added 6 commits July 26, 2025 12:35
- 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.
@jtracey93 jtracey93 self-assigned this Jul 28, 2025
@jtracey93 jtracey93 added Status: Do Not Merge ⛔ Do not merge PRs with this label attached as they are not ready or aligned to future direction etc. Type: Documentation 📄 Improvements or additions to documentation Type: Feature Request ➕ New feature or request and removed Needs: Triage 🔍 Maintainers need to triage still labels Jul 28, 2025
@@ -0,0 +1,186 @@
---
draft: true
Copy link
Contributor

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 👍

Comment on lines +110 to +118
<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;" />
Copy link
Contributor

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)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Links to them?

Copy link
Contributor

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

Comment on lines +184 to +186
### 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.
Copy link
Contributor

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
Copy link
Contributor

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

Copy link
Contributor

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

  1. AVM module owners
  2. AVM module consumers

As they both will use very differently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Do Not Merge ⛔ Do not merge PRs with this label attached as they are not ready or aligned to future direction etc. Type: Documentation 📄 Improvements or additions to documentation Type: Feature Request ➕ New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants