Configurable default Taskfile

[HeCorr]

IMO the default Taskfile (generated with --init) is not very useful out-of-the-box:

Taskfile.yml

# https://taskfile.dev

version: '3'

vars:
  GREETING: Hello, World!

tasks:
  default:
    cmds:
      - echo "{{.GREETING}}"
    silent: true

I always end up editing it like this to get a good starting point:

Cleaner Taskfile.yml

# https://taskfile.dev

version: '3'

-vars:
-  GREETING: Hello, World!
-
tasks:
  default:
    cmds:
-      - echo "{{.GREETING}}"
+      - task --list
    silent: true

Now simply calling task lists all available tasks that have a description.

So it would be very useful to be able to specify a default "template" to use with the --init flag, maybe stored in the user's home directory.

[HeCorr]

Since I plan on making use of the -t, --taskfile flag in #2008, I can probably use the -g, --global flag instead, which when supplied together with --init will copy the file at $HOME/Taskfile.template.yml.

The only downside I see with this is having to add extra info to the -g flag's description which might make it excessively long.

Also I'm not quite sure how testable this will be since the path to $HOME would be hard-coded.

Thoughts?

[andreynering]

Hi @HeCorr,

Some thoughts:

• We could consider simply improve that default template.
• In theory, we could have more templates for different types of projects: Go, Ruby on Rails, Docker, etc. Could be easily implemented by having a directory on the Task repository embeded using go embed. We could allow it to be overriden by $HOME/.task/templates or a directory passed by parameter.

We could create an issue to track the idea. What do you think?

[HeCorr]

yep, that would work :)

[andreynering]

#2012