Skip to content

CLI: no need to implicitly specify =true for commandline flags #357

CLI: no need to implicitly specify =true for commandline flags

CLI: no need to implicitly specify =true for commandline flags #357

Triggered via pull request December 2, 2024 05:29
Status Success
Total duration 4m 39s
Artifacts

sanity.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors
build
use BeforeEach() to assign variable vWhen
build
use BeforeEach() to assign variable vContext
build
ginkgo-linter: "Expect": missing assertion method. Expected "To()", "ToNot()" or "NotTo()"
build
ginkgo-linter: "Eventually": missing assertion method. Expected "Should()" or "ShouldNot()"
build
ginkgo-linter: Success matcher only support a single error value, or function with Gomega as its first parameter
build
ginkgo-linter: wrong error assertion. Consider using `Eventually(func() error { return err }).Should(Succeed())` instead
build
ginkgo-linter: Success matcher does not support multiple values
build
ginkgo-linter: Success matcher only support a single error value, or function with Gomega as its first parameter
build
ginkgo-linter: wrong error assertion. Consider using `Eventually(func() error { return err }).Should(Succeed())` instead
build
ginkgo-linter: Success matcher does not support multiple values