I think I found sth that may be much more elegant solution to the problem I have. Here, I use alias (or label) on task itself and I can use variables to simply substitute it with any name I want when it is executed using deps or direct call. Example Taskfile with the syntax:

version: '3'
tasks:
  default:
    deps:
      - task: test
        vars: 
          ALIAS: IAMDEPTASK
    cmds:
      - task: test
        vars: 
          ALIAS: IAMSUBTASK
      - task: test
  test:
    alias: "{{.ALIAS}}"
    sources:
      - Taskfile.yml
    generates:
      - Taskfile.yml

As you may see, implementation is minimal and modifies just task struct but nothing else. Another advantage is it can be used to customize task name in every context, even if task is called directly.

Problems I found so far: in example above, last task currently generates message task: Task "<no value>" is up to date while it should use original name of the task in such case. But that seems trivial to fix.

I leaved all changes in this branch so far waiting for any comments, but if accepted only last commit will be one proposed to merge (updated with tests, documentation etc. if required).

Hi @adamwasila,

I liked this approach, it seems really simple.

I like label much more than alias, though, specially because there's another feature request that would be called "alias" (#268) and this name makes more sense there than here.

Thanks for your comments. I have implemented it accordingly and it is ready for review now.

Hi @adamwasila,

Seems great, thanks! ❤️