Fake file generation breaks project

[apexskier]

If I change the interface of a module, I start getting build errors for the autogenerated fake implementations, as I'd expect. However, if I regenerate these files and proceed, the freshly generated files break the project.

A minimal reproduction:

From the cli directory

> cd cli

A build succeeds

> opctl run build

Don't make any real changes for this example.

Regenerate the fake clicolorer implementation (this also will reproduce similarly for other fake implementations)

> rm internal/clicolorer/fake.go
> opctl run -a path=internal/clicolorer/cliColorer.go generate

Now, building fails and cli/internal/clicolorer/fake.go has about 278 changed lines.

> opctl run build

import cycle not allowed
package github.com/opctl/opctl/cli
	imports github.com/opctl/opctl/cli/internal/clicolorer
	imports github.com/opctl/opctl/cli/internal/clicolorer
can't load package: import cycle not allowed
package github.com/opctl/opctl/cli
	imports github.com/opctl/opctl/cli/internal/clicolorer
	imports github.com/opctl/opctl/cli/internal/clicolorer

[apexskier]

maxbrunsfeld/counterfeiter#103