chore(workflows): simplify Copilot setup steps workflow triggers (#414)

katriendg · web-flow · commit 492a7b103274 · 2026-02-04T15:39:36.000+01:00
## Description Streamlined the `copilot-setup-steps.yml` workflow configuration based on MAUI team guidance and official GitHub documentation. The workflow now uses only `workflow_dispatch` for manual validation, aligning with how Copilot coding agent internally executes setup steps (not through visible workflow triggers). Added resilience improvement: `continue-on-error: true` on the npm dependency installation step allows Copilot to start work even when dependencies fail, enabling it to fix `package.json` or `package-lock.json` issues itself. ## Related Issue(s) Closes #411 ## Type of Change Select all that apply: **Code & Documentation:** - [ ] Bug fix (non-breaking change fixing an issue) - [ ] New feature (non-breaking change adding functionality) - [ ] Breaking change (fix or feature causing existing functionality to change) - [ ] Documentation update **Infrastructure & Configuration:** - [x] GitHub Actions workflow - [ ] Linting configuration (markdown, PowerShell, etc.) - [ ] Security configuration - [ ] DevContainer configuration - [ ] Dependency update **AI Artifacts:** - [ ] Reviewed contribution with `prompt-builder` agent and addressed all feedback - [ ] Copilot instructions (`.github/instructions/*.instructions.md`) - [ ] Copilot prompt (`.github/prompts/*.prompt.md`) - [ ] Copilot agent (`.github/agents/*.agent.md`) **Other:** - [ ] Script/automation (`.ps1`, `.sh`, `.py`) - [ ] Other (please describe): ## Sample Prompts (for AI Artifact Contributions) N/A - Infrastructure change only. ## Testing - Verified workflow file syntax is valid YAML - Manual dispatch trigger can be used to validate setup steps work correctly - Copilot session logs will show setup steps execution when agent starts work ## Checklist ### Required Checks - [x] Documentation is updated (if applicable) - [x] Files follow existing naming conventions - [x] Changes are backwards compatible (if applicable) - [ ] Tests added for new functionality (if applicable) ### AI Artifact Contributions N/A - Not an AI artifact contribution. ### Required Automated Checks The following validation commands must pass before merging: - [ ] Markdown linting: `npm run lint:md` - [ ] Spell checking: `npm run spell-check` - [ ] Frontmatter validation: `npm run lint:frontmatter` - [ ] Link validation: `npm run lint:md-links` - [ ] PowerShell analysis: `npm run lint:ps` ## Security Considerations - [x] This PR does not contain any sensitive or NDA information - [ ] Any new dependencies have been reviewed for security issues - [x] Security-related scripts follow the principle of least privilege ## Additional Notes Reference sources for these changes: - [MAUI team Copilot tips](https://devblogs.microsoft.com/dotnet/maui-team-copilot-tips/) - Guidance on `continue-on-error` and workflow structure - [GitHub Docs: Customizing the development environment](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment) - Official specification 🔧 - Generated by Copilot
diff --git a/.github/workflows/copilot-setup-steps.yml b/.github/workflows/copilot-setup-steps.yml
@@ -7,15 +7,10 @@
 
 name: "Copilot Setup Steps"
 
-# Auto-run on push/PR to validate the setup workflow
+# Copilot coding agent runs these steps internally before starting work.
+# Use workflow_dispatch to manually validate the setup when desired.
 on:
   workflow_dispatch:
-  push:
-    paths:
-      - .github/workflows/copilot-setup-steps.yml
-  pull_request:
-    paths:
-      - .github/workflows/copilot-setup-steps.yml
 
 jobs:
   # Job MUST be named 'copilot-setup-steps' to be recognized by Copilot
@@ -38,7 +33,10 @@ jobs:
           node-version: "20"
           cache: "npm"
 
+      # continue-on-error allows Copilot to start work even if dependencies fail,
+      # so it can fix package.json/package-lock.json issues itself
       - name: Install JavaScript dependencies
+        continue-on-error: true
         run: npm ci
 
       - name: Set up Python
