Re-run checks if changes are applied

[brynary]

No description provided.

[qltysh]

The code coverage on the diff in this pull request is 75.0%

Drilldown

Path	File Coverage Δ
qlty-cli/src/ui/text.rs	1.3
qlty-cli/src/ui/fixes.rs	0.4
qlty-check/src/tool/command_builder.rs	-2.6
qlty-check/src/tool/ruby/sys/macos.rs	-3.1
qlty-cli/src/commands/check.rs	1.2
qlty-check/src/tool/download.rs	-0.7
qlty-check/src/executor/driver.rs	0.9
qlty-check/src/tool/ruby/sys/linux.rs	1.6
qlty-check/src/parser/clippy.rs	-0.3

[brynary]

@lsegal I am seeing a strange test failure on Windows:

---- expected: stdout
++++ actual:   stdout
   1    1 |  ERRORS: 1 
   2    2 | 
   3    3 | exists  Error  Exited with code 0 in [..].[..]s  .qlty/out/invoke-[..].yaml
   4      -         The plugin crashed for some reason
        4 +         "The plugin crashed for some reason"

This is straightforward enough... The output does not match the snapshot, because the actual output is rendering quotes around line 4. However, this does not seem to happen on Mac or Linux, and I am not aware of any behavior which would cause printing output to vary on Windows vs. other platforms.

This is the line where the output is origininating:

tw.write_all(format!("\t{}", style(line).red()).as_bytes())?;

[qltysh]

3 new issues

Tool	Category	Rule	Count
qlty	Structure	High total complexity (count = 61)	1
qlty	Structure	Function with high complexity (count = 30): execute	1
qlty	Structure	Deeply nested control flow (level = 5)	1

qlty successfully analyzed this pull request in 2m.