Ability to re-run a commit if it fails

[lricoy]

Sometimes, when a pre_commit hook is configured, our commit will fail. It would be helpful to have a way to pass something like --retry so we won't need to enter the message again.

[jimthedev]

Good point. Since this is a cli, we don't really have any place to store this commit over time. Would it be just the last 1 commit that you'd want cached?

[lricoy]

Yeah, at first that would be the case. The use case would be to re-run it after fixing the tests or coverage. If you want to give me some direction and tell me how or where to store it I may give it a try and add that functionality myself. Something like @kentcdodds wrote on his article.

[kentcdodds]

I'd love this feature. Having to fill out the prompts again because of a long error is super annoying. I'd want it to show me the message before it commits though.

[jimthedev]

Where can we store this info? A text file cache in the repo? We'd need to add it to .gitignore but at least then the cash would go with the repo if it gets moved.

[kentcdodds]

Yeah, put it in the repo and document the need to gitignore it

[jimthedev]

Gave it a bit more thought. We can do this simply by have a filesystem based cache in the user's home directory.

The cache keys will be a paths to repo roots, the value will be a serialized command that was going to be executed. I will work on this soon. I think we can offer it w/o a breaking change or .gitignore changes. Sure if you move a folder around you'll lose the ability to use the retry command between moves, but that probably an ok tradeoff.

[kentcdodds]

What if you used the temp directory instead? That way you don't put more stuff in the already-too-full user home...

[jimthedev]

I'm thinking of using home-or-tmp.
On Wed, Mar 9, 2016 at 8:19 PM Kent C. Dodds notifications@github.com
wrote:

What if you used the temp directory instead? That way you don't put more
stuff in the already-too-full user home...

—
Reply to this email directly or view it on GitHub
#132 (comment).