Configurable Fail Strategy for non-dependent tasks

[d3rpp]

Goals

1. Allow multiple tasks that may fail to run in parallel without affecting each other

e.g. Format Checking / Linting tasks should run to completion even if sibling tasks fail

Non-goals

1. Allow a dependent task to run even if a previous task fails

Background

All formatting tasks in my monorepo are unaffected by each other, so it makes sense that if run in parallel, the exiting with a non-zero exit code of one should not lead to the exiting of another.

Workaround

Within the scripts you can append a || true or || echo '' which overwrites the status code, though this does make it harder to see if something does fail at a glance since it is marked as successful.

Proposal

This could be implemented by configuring a job as something like can_fail so a failure in the task will only affect dependent tasks, but not unrelated tasks being run in parallel.

I'd be happy to contribute though may need a bit of a hand at first navigating the repo.

[chris-olszewski]

Does --continue suit your needs? Documentation

[d3rpp]

Hi,

Yes this suits my requirements perfectly. I suppose my question then becomes something along the lines of "can we make this a part of the task config turbo.json"?

I'm apologise I definitely should've checked for a CLI flag in the docs 😄