Andrew Poydence

This PR will allow a user to create a hierarchy of `PrePersistentRun` and `PostPersistentRun`. Meaning if the root and sub command both have a hook, then both will be invoked....

Is there any chance of this being merged?

Yes. However, I think given the name "Persistent", it shouldn't be required. PersistentFlags for example don't have to be added in this way.

Would still love for this to be considered.

I think I would want that or an option to not include the go generate line

Does that imply the go generate line should be removed from the generated output?

@profsmallpine Please feel free to open an issue to discuss and propose what you are needing. From there, we should be able to sort out what PRs we should do....

@msabramo This has not actually been fixed yet. The commit referencing this issue was in poy/mock and not golang. I wasn't happy with it, so I never made the PR.

A few that come to mind: * Reversing the order in which mocks are registered (to match gmock for example) * Reporting styles (verbose vs quiet)

Have you looked at the `gomock.Do()` ([docs](https://godoc.org/github.com/golang/mock/gomock#Call.Do))? It seems like this would get you pretty close.