Menu
Validate every meaningful workflow_dispatch input combination before approving release-pipeline changes
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Drive package defaults, release packaging, and website version display from one MSBuild property
Keep mixed validation/release GitHub workflow dispatch inputs from misrouting validation runs
Validate NuGet release artifacts before publish and ensure both package and symbol payloads are release-correct
Ship an Astro docs site to GitHub Pages with SEO, validation, and custom-domain safety checks
Keep repo-local .NET sample apps zero-config by avoiding native apphosts when macOS integrity enforcement can kill them
Avoid `.App` executable assembly names for runnable .NET samples on macOS
| name | workflow-dispatch-input-matrix |
| description | Validate every meaningful workflow_dispatch input combination before approving release-pipeline changes |
| domain | release-engineering |
| confidence | high |
| source | tank-earned |
When a GitHub Actions workflow branches on workflow_dispatch inputs, validate the full input matrix instead of only the expected happy path.
Minimum matrix:
Release workflows often hide bugs in guard clauses, especially when a single optional input changes the entire decision tree. A matrix check catches “works for release, breaks for validation” regressions before the failure shows up in GitHub.
Do not approve a release-workflow fix unless the reported failing tuple is shown to pass or is intentionally blocked with clearer, documented behavior.
