devcontainers / devcontainers/ci

"Everything in one step" approach clashes with workflows where the dev container is treated as one target platform.

Abierto
#281 7 comentarios 2 reacciones 1 asignado Reclamado por @chrmarti Ver en GitHub
feature
Lenguaje dominante
TypeScript
Estrellas
497
Forks
102
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.