Provide a flag to control generation of the invocation comment

[skitt]

The invocation comment stores the complete details of all provided arguments, which may include paths to files. These aren't always consistent, which results in unwanted changes in the generated files (especially for CI checking for unexpected changes...).

Since the invocation isn't always useful, provide a flag to control whether the comment is generated. To preserve current behaviour this defaults to true (enabled).

Fixes #104.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ewhauser]

@skitt - Can you sign the CLA so that this gets merged? Thank you!

[tchung1118]

LGTM. Will be merged once author signs CLA.

[skitt]

@skitt - Can you sign the CLA so that this gets merged? Thank you!

I’m just waiting for our legal department to check it.

[sodul]

@skitt any progress on the CLA? We are staying at v0.2.0 until there is a new release with this fix.

[skitt]

@skitt any progress on the CLA? We are staying at v0.2.0 until there is a new release with this fix.

It’s still pending, sorry...

[sodul]

@JacobOaks I've created an alternate PR (#153) against the latest main (no conflicts) and have signed the CLA. This should allow for mockgen to be released with this issue fixed for good.

FYI, I have contributed to the project before the ownership transfer.

[JacobOaks]

Hey @skitt, closing as superceded by #153. Thanks!

[skitt]

That’s fine @JacobOaks, thanks @sodul for proposing an alternate PR!