John Brunton

For local dev, cloning repos on every invocation can be tedious with larger repos. Some mechanism for caching/updating local repos might be useful.

While it very slightly simplifies setup for some users, there are some significant downsides to bundling ytt and jsonnet into the binary: * It significantly slows compilation. * The binary...

Either to optionally include, or optionally exclude, specific workflows. Perhaps a package could also specify which to export by default.

Perhaps replace with an existing logging framework. This may help avoid duplication between gflows and g3ops.

Using the example package requires additional files and creates dependencies on external code. Better to define the packages in the tests themselves.

Per comment in GFlowsLib: ``` // TODO: Description should be SourcePath if remote, relative SourcePath if within context dir (i.e. in source control), // and in terms of library name...