feat: Continue with error

[ianzone]

⚡ Summary

Some jobs may fail but shouldn't block hooks.

Value

provide continue option for each job

Behavior and configuration changes

jobs:
  - name: audit
    run: bun audit
    continue: true

If run fails, other jobs won't be affected, and there should be warnings about this job in the summary.

[otg996]

Just providing some feedback here.

From a UX perspective I support adding a continue option.
From my personal biases I don't support it and think it should be the user's responsibility to define this kind of behavior.

In the meantime, you can create non-blocking steps using shell command grouping. This will force a command to succeed while still printing its failure message.

# lefthook.yml
  jobs:
    - name: audit
      # Fails with a warning but allows other hooks to run.
      run: bun audit || { echo "⚠️ bun audit failed, but continuing..."; true; }

The limitation is that the summary will show success.

[mrexox]

@ianzone , could you share the use case? Do you need an ability to continue some of the jobs while breaking the pipeline on others?

[ianzone]

@ianzone , could you share the use case? Do you need an ability to continue some of the jobs while breaking the pipeline on others?

Currently, if any "run" exit with none 0, all jobs will be terminated. I wish to mark certain jobs as "continue: true" or "breakOnFail: false", so even if they are failed, other jobs won't be cancelled. And also, the error msg should be listed in the final summary.

[mrexox]

@ianzone , that’s the default behavior if you don’t specify piped: true option. Maybe without a message, but there’s a fail_text option for that. Do you have piped: true in your configuration?

[ianzone]

@ianzone , that’s the default behavior if you don’t specify piped: true option. Maybe without a message, but there’s a fail_text option for that. Do you have piped: true in your configuration?

No, jobs are paralleled, I misdescribed, I mean it will cancel following git hooks. Eg if any job in pre-commit failed, the prepare-commit-msg won't run.

[mrexox]

Oh, I see, so I think the workaround can be used now. I will consider this feature. It’s exiting with code 0 even if the job failed.