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: ``` yaml #### 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: ``` yaml - 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.)
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by kazmasaurus and has received 10 comments.