Daniel Antos
@danielantos.bsky.social
Thanks!
CI gets simpler overall - most of the setup boilerplate disappears from jobs (and Dockerfiles). However, to combat possible developer errors, you need one special job to check committed generated code and dependencies (like you said).
CI gets simpler overall - most of the setup boilerplate disappears from jobs (and Dockerfiles). However, to combat possible developer errors, you need one special job to check committed generated code and dependencies (like you said).
September 14, 2024 at 11:34 AM
Thanks!
CI gets simpler overall - most of the setup boilerplate disappears from jobs (and Dockerfiles). However, to combat possible developer errors, you need one special job to check committed generated code and dependencies (like you said).
CI gets simpler overall - most of the setup boilerplate disappears from jobs (and Dockerfiles). However, to combat possible developer errors, you need one special job to check committed generated code and dependencies (like you said).