"calling run inside a local task will have the same effect as calling runLocally"

[staabm]

just stumbled over this "note" in the docs
https://deployer.org/docs/tasks.html#local-tasks

I find it really supprising that run - one of the most often used commands - can change meaning depending on whether we are running a local task or not.

IMO the code would be better understandable/readable when run would throw a exception in a local task and runLocally would be required to use, no matter whether a task is local or not.

is this just "syntactic sugar" or is this magic-behaviour required/usefull?
is this something you are willing to change with the new majoar 7.x which is still in a kind of beta-state?

[antonmedv]

I also find local task not useful. What about deleting such feature in v7?

[staabm]

(Or at least deprecated for now)

[staabm]

Do you agree with deprecating it first? Or should it be removed without prior deprecation?

[antonmedv]

I’m still thinking about it. There is a case there you want a task without host. For notify for example.

[staabm]

In which case one could still use runLocally() without marking the task as local(), no?

[antonmedv]

This is true.