Add GitHub Copilot setup steps workflow for .NET 9 environment - #6
Conversation
Co-authored-by: Geertvdc <8984505+Geertvdc@users.noreply.github.com>
Geertvdc
left a comment
There was a problem hiding this comment.
instead of doing these steps can we use container: instead that uses our devcontainer? this already contains .net 9
|
|
||
| # You can define any steps you want, and they will run before the agent | ||
| # starts. If you do not check out your code, Copilot will do this for you. | ||
| steps: |
There was a problem hiding this comment.
Can't we use the dev container instead of steps that install .net every time?
There was a problem hiding this comment.
Yes, good point! Updated the workflow to use the devcontainer image instead of manually installing .NET every time. The workflow now uses container: mcr.microsoft.com/devcontainers/dotnet:1-9.0-bookworm which matches the devcontainer setup. Commit: 825e266
Co-authored-by: Geertvdc <8984505+Geertvdc@users.noreply.github.com>
Changed the workflow to use |
This PR adds a GitHub Actions workflow that sets up the development environment for GitHub Copilot coding agents to work with .NET 9, matching the existing devcontainer configuration.
Changes Made
.github/workflows/copilot-setup-steps.ymlworkflow fileactions/setup-dotnet@v4copilot-setup-stepsfor proper Copilot recognitioncontents: read) for security best practicesWorkflow Features
The workflow ensures GitHub Copilot coding agents have access to:
Testing
yamllintThis provides GitHub Copilot with the same .NET 9 environment that developers get when using the devcontainer, ensuring consistent coding assistance.
Fixes #5.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.