Dean Malmgren

Sorry it took me so long to circle back to this. I've had a crazy couple of weeks at work and this thread got buried in my inbox. I believe...

If either of you would like to step in to help, I would greatly appreciate it. My work has taken me away from the world from extracting text out of...

#22 should address this as well, I think.

I started to get the source code in `examples/image-colors` implemented but I haven't been able to start enabling this feature within workflow itself yet

After spending a decent amount of time coding this up and playing with it in practice, I'm not terribly convinced that this is the best way to approach this issue....

Maybe we could also support something like this to make the notation more compact for situations in which you only have one tag: ``` yaml --- creates: a/figure depends: another/file...

@gabegaster noting this for posterity, but as we discussed this is slightly undesirable because then it makes it difficult to build on the `figures` pseudotask. @bjlange had another idea which...

got rid of pseudotasks in d4434ee8801ff4c6bbc11cf7fa300104b8a5c75e, which is the last foreseeable backwards incompatible change before releasing v1.0.0 also, one possibility for the `batches.yaml` concept would be to put those in...

Also, @laurieskelly suggested including a `--quieter` option to suppress some of the output to only the essential chunks.

This should be pretty easy now that we've started to separate things into subcommands. What would you think of a command line interface that looked like this: ``` bash workflow...