Create github copilot setup workflow#26285
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new GitHub Actions workflow that establishes standardized environment setup steps for GitHub Copilot's coding agent. The workflow enables testing and validation of the Copilot setup process directly from the repository's Actions tab.
Key Changes:
- Added a new workflow file that defines the required
copilot-setup-stepsjob - Implements the standard PowerShell build prerequisites: checkout with sufficient history, .NET setup, and tag synchronization
- Configured to run manually via
workflow_dispatchfor testing purposes
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
iSazonov
left a comment
There was a problem hiding this comment.
Could be useful:
# Install global tools that might be useful for development
- name: Install useful .NET tools
continue-on-error: true
run: |
dotnet tool install --global dotnet-format
# Setup PATH to include .NET tools
- name: Setup PATH
run: |
echo "$HOME/.dotnet/tools" >> $GITHUB_PATH
# Diagnostics in the log
- name: Show .NET info
run: dotnet --info
- name: Setup completed
run: |
echo "✅ Copilot setup completed successfully!"
|
@TravisEz13 Please look that Copilot ask to enable in its firewall Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
If this is needed, add to start-psbootstrap as a new or existing scenario |
Refactor CI setup steps to include logging and environment setup.
Co-authored-by: Travis Plunk <[email protected]>
| # Both: Package and DotNet scenarios | ||
| # Tools: Install .NET global tools (e.g., dotnet-format) | ||
| # All: Install all dependencies (packaging, .NET SDK, and tools) | ||
| [ValidateSet("Package", "DotNet", "Both", "Tools", "All")] |
There was a problem hiding this comment.
As we discussed offline, the Both value should be remove, so that
- for dev/CI, we can use
-Scenario All - for official build, we must use individual scenario explicitly
The cleanup can be done in a separate PR.
Ideally, this parameter should be made a flags Enum, so a caller can provide arbitrary combination :)
|
📣 Hey @@TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
Co-authored-by: Dongbo Wang <[email protected]>
Co-authored-by: Dongbo Wang <[email protected]>
Co-authored-by: Dongbo Wang <[email protected]>
PR Summary
This pull request introduces a new GitHub Actions workflow for Copilot setup. The workflow, defined in
.github/workflows/copilot-setup-steps.yml, allows you to test and customize the environment setup steps for Copilot from your repository's Actions tab.New Copilot setup workflow:
.github/workflows/copilot-setup-steps.ymlto define a workflow named "Copilot Setup Steps" that runs onworkflow_dispatchand sets up the environment before Copilot starts.global.json, and runs a PowerShell bootstrap script to install dependencies and synchronize PowerShell tags.PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header