Env variable for absolute path of current working directory.

[lesomnus]

Assume I run following taskfile at /home/lesomnus/foo:

version: "3"

tasks:
  hello:
    dir: bar
    cmds:
      - echo $(pwd)

It will print /home/lesomnus/foo/bar where the cmd's working directory.
However, I believe it can be templated without executing pwd.

There was an issue about it at #525 but is closed as duplication of #215 but #215 does not state that.

Maybe I can:

version: "3"

tasks:
  hello:
    dir: bar
    vars:
      PWD:
        sh: pwd
    cmds:
      - echo {{.PWD}}

but it is too verbose.

Is there already a special variable for this?

[mgbowman]

Is USER_WORKING_DIR what you're looking for?

https://taskfile.dev/usage/#running-a-taskfile-from-a-subdirectory

https://taskfile.dev/reference/templating/#special-variables

[vmaerten]

From what I understand, you’re looking for the path where the execution will occur.
Currently, there isn’t a specific variable for this. However, it could be a good addition.

The USER_WORKING_DIR variable will return /home/lesomnus/foo.

[lesomnus]

I modified the question slightly because I think the question was written confusingly.
Anyway, I think you understood my question correctly, and it seems that there is no predefined variable that I want.

I don't think the cost of executing pwd is that big, but it would be nice if the current path is substituted into the cmd script so that the path is displayed (rathern thatn "$(pwd)") in the output.