Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: run in fail-fast and non-block by default #191

Open
cristianoliveira opened this issue Jul 12, 2024 · 0 comments
Open

feat: run in fail-fast and non-block by default #191

cristianoliveira opened this issue Jul 12, 2024 · 0 comments
Labels
breaking-change feature A feature idea or request

Comments

@cristianoliveira
Copy link
Owner

cristianoliveira commented Jul 12, 2024

BREAKING CHANGE: the watcher won't run all tasks but report back on the first failing one

The breaking change is subtle but if one relies on the old behavior of always running all tasks, it's a breaking for them, we'll provide option flags to do so

Reasoning:

I get myself using this form of workflow like TDD red -> green -> refactor:

  1. Change code
  2. Run all checks
  3. Is there a failing check? Then go to 5 (RED), else go to 4
  4. Add to git and commit (GREEN)
  5. Fix what failing the checks (REFACTOR) and go to 2

And with --fail-fast it gives you a nice flow where you "Fix the next failing thing" till all checks are GREEN

@cristianoliveira cristianoliveira added feature A feature idea or request breaking-change labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change feature A feature idea or request
Projects
None yet
Development

No branches or pull requests

1 participant