#Dogfooding in Progrock repo

1 messages · Page 1 of 1 (latest)

sour cedar
#
  • It'd be nice if I could just run dagger do test instead of passing -p on every command. Maybe we could support this with a config tweak? I basically want to put my CI code under ./ci/ but still use c.Host().Directory(".") to refer to the repo root, i.e. ./ci/../.
#
  • dagger do generate runs go generate ./.... go generate creates/updates files all over the repo without a clear output directory, so this is technically "overlaying" the entire repo over itself. It works, and felt natural to implement, but I'm curious if this is efficient! Maybe filesync's diffing protocol is doing its job?
#
  • The TUI definitely feels pretty verbose for some operations. I like seeing the test output from dagger do test, but dagger do generate is pretty uninteresting. There's also a lot of noise from dagger do plumbing. The "focus" UI could help here.