Skip to content

Credo.Check format_issue can use a custom exit_status option #66

Credo.Check format_issue can use a custom exit_status option

Credo.Check format_issue can use a custom exit_status option #66

Re-run triggered November 20, 2024 19:57
Status Failure
Total duration 1m 27s
Artifacts

housekeeping.yml

on: pull_request
used mix format
35s
used mix format
tested that for each check there is at least one trigger assertion
19s
tested that for each check there is at least one trigger assertion
tested that for each check all params are covered by tests
18s
tested that for each check all params are covered by tests
all triggers are looked up and confirmed
25s
all triggers are looked up and confirmed
compiling deps shows no compiler warnings (optional)
28s
compiling deps shows no compiler warnings (optional)
resulting issues are still the same (optional)
1m 15s
resulting issues are still the same (optional)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 8 warnings
used mix format
Process completed with exit code 1.
resulting issues are still the same (optional): lib/credo/check/refactor/long_quote_blocks.ex#L111
Function body is nested too deep (max depth is 2, was 3).
resulting issues are still the same (optional): lib/credo/check/design/alias_usage.ex#L230
Function takes too many parameters (arity is 10, max is 8).
resulting issues are still the same (optional): lib/credo/cli/options.ex#L77
Function takes too many parameters (arity is 9, max is 8).
resulting issues are still the same (optional): lib/credo/cli/options.ex#L54
Function takes too many parameters (arity is 9, max is 8).
resulting issues are still the same (optional): lib/credo/check/design/alias_usage.ex#L226
Function takes too many parameters (arity is 9, max is 8).