Named groups of tasks

Something I’m currently doing is grouping related commands by their goal rather than their type, i.e. instead of having all the links together, I have:

#### vim ####
- shell:
    - [git submodule update --init --recursive "vim/vim-plug", Installing vim-plug]
- link:
    ~/.vimrc: vim/.vimrc
    ~/.vim/autoload/plug.vim: vim/vim-plug/plug.vim

### fish ###
- link:
    ~/.config/fish/config.fish: fish/config.fish

While this works great, it leads to the output of dotbot not being as easy to parse:

• It’s pretty hard to see where one goal ends and the next begins, even with the green success messages.
• The success messages aren’t a great fit for repetition, it’s a little weird to see “All commands have been executed” multiple times.

Given this, it would be cool to lift this sort of jobs pattern into dotbot itself, so that dotbot can intelligently group output based on the jobs. I’m thinking something like this:

- jobs:
    vim: 
        - shell:
            - [git submodule update --init --recursive "vim/vim-plug", Installing vim-plug]
        - link:
            ~/.vimrc: vim/.vimrc
            ~/.vim/autoload/plug.vim: vim/vim-plug/plug.vim
    fish:
        - link:
            ~/.config/fish/config.fish: fish/config.fish

(I’m not particularly for or against the top level jobs task, but it seems like the easiest way to fit into the current plugin capability.)

[ghalestrilo]

Great! I’m on it!

[anishathalye]

I have similar thoughts as expressed in https://github.com/anishathalye/dotbot/issues/225#issuecomment-653208889 and https://github.com/anishathalye/dotbot/issues/35#issuecomment-171951443. tl;dr I don’t really want the YAML config file to slowly grow into a programming language embedded in YAML (e.g. like Ansible). If we really do need those generic programming language constructs like conditionals, perhaps a better solution is to create a DSL embedded in a real programming language (Python, or maybe something else). It’s a tricky design decision to figure out exactly what features to include in our YAML config file. I want to spend a bit more time thinking about that before complicating the semantics of the YAML config any further. Would love to hear your thoughts on this. (I’ve been a bit busy recently; I hope to have a slightly more concrete proposal than the hypothetical examples in https://github.com/anishathalye/dotbot/issues/35#issuecomment-171951443 soon.)