The warning prompt occurs after the dependencies have been executed.

[Arnaud-IFEA]

• Task version: v3.39.0
• Operating system: Debian
• Experiments enabled: none

Since #1657 the warning prompt for a task happened after the preconditions (and that make sense :) ), but also after the dependencies.

This is a bit annoying for two reasons:

• dependencies are sometimes long tasks that we don't want to run for nothing in the end.
• deps are sometimes used just to run tasks in parallel, so they're not really dependencies...

What do you think ? Does it make sense to display the prompt before the dependencies ? Or maybe adding an option to perform tasks in // in cmds: ?

Regards.

[evilhamsterman]

It's not just that the warning won't run until the deps have completed. Preconditions don't run at all until after the deps have completes. Same thing with status, the deps always run first then preconditions and status are checked. Status and preconditions should run be for anything else, then if they pass start running deps and commands.