@viveksinghggits could you please review this PR?

pkg/field/field_test.go:7: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	. "gopkg.in/check.v1"

pkg/field/field_test.go:9: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	"github.com/kanisterio/kanister/pkg/field"

pkg/poll/poll_test.go:25: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	"github.com/jpillora/backoff"

how to fix this one ?

@saima-s can you have a look into this please and try to get it merged.

@viveksinghggits could you please review this PR?

pkg/field/field_test.go:7: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	. "gopkg.in/check.v1"

pkg/field/field_test.go:9: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	"github.com/kanisterio/kanister/pkg/field"

pkg/poll/poll_test.go:25: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kanisterio/kanister) -s blank -s dot (gci)
	"github.com/jpillora/backoff"

how to fix this one ?

gci linters expects imports to be in order as mentioned here.
You can arrange imports in the order from this to something like:

        "context"
	"fmt"

	"github.com/kanisterio/kanister/pkg/field"

        . "gopkg.in/check.v1"

@saima-s do i need to fix above issue i was facing , because there are so many files having this isssue .
Do we have any tool which does everything based on below rule ?

 gci:
    sections:
      - standard
      - default
      - prefix(github.com/kanisterio/kanister)
      - blank
      - dot

@julio-lopez test file are yet to update.
let me fix everything and then I will push all the changes .

@julio-lopez All set . Now, could you please test it ?

@julio-lopez

if err := os.Setenv(kube.PodNSEnvVar, "test"); err != nil {
    t.Fatalf("Error setting env variable: %v", err)
}

Would this approach fine ?

Would this approach fine ?

This is preferred whenever possible

err := os.Setenv(kube.PodNSEnvVar, "test")
c.Assert(err, IsNil)

Would this approach fine ?

This is preferred whenever possible

err := os.Setenv(kube.PodNSEnvVar, "test")
c.Assert(err, IsNil)

Then , can I replicate through all test file ?

@julio-lopez done . Could you please review ?

@julio-lopez Done sir. And one thing i confused about is which issue to mention while raising next PR. if i mentioned issue 2962 then it will automatically closed once it get merged and but we want that issue will close, once all PR get merged . could you suggest me ? . so , that i could aware about in next PR. Thankyou

@julio-lopez Done sir. And one thing i confused about is which issue to mention while raising next PR. if i mentioned issue 2962 then it will automatically closed once it get merged and but we want that issue will close, once all PR get merged . could you suggest me ? . so , that i could aware about in next PR. Thank you

Reference the issue simply as #2962 , do not prepend "Fixes" or "Closes" and you should be OK.