devcontainers / devcontainers/ci
"Everything in one step" approach clashes with workflows where the dev container is treated as one target platform.
Offen
feature
- Vorherrschende Sprache
- TypeScript
- Sterne
- 496
- Forks
- 101
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
It's awkward that, if there are 10 linearly-dependent steps to testing my project, I have to put them all into one devcontainer `runCmd` when the devcontainer is treated as a target platform in my matrix strategy. All the other platforms get distinct workflow steps but I have to intentionally not run any of those on the dev container and instead run one unified step.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.