The error message it gives seems to explain the issue. I'm not certain if we can really plan for that type of failure

I would expect git-town to roll back any previous actions if possible

Any idea as to why this occurred on git checkout remove-jose (which is being ran at the end to preserve the checkout history) instead of the previous checkout commands?

nope, I was not running any parallel git functions which is why this tripped me.

@arekkas did you have another Git client open, like IntelliJ of Github Desktop? They sometimes perform Git commands in the background. Git isn't thread-safe, it errs out when another Git process is currently doing something in the same repo.

@charlierudolph what do you think about automatically retrying (for like 3 times or so) when we encounter this error (with a 1 second delay in between runs to give the other Git process time to finish)?

Yes, IntelliJ was open, maybe that caused the issue!

@charlierudolph what do you think about automatically retrying (for like 3 times or so) when we encounter this error (with a 1 second delay in between runs to give the other Git process time to finish)?

@kevgo I'm not certain what commands we would do that with. Not all commands can be retried immediately and many fail for different reasons. I think the better approach would be just to plan for this error and allow abort / continue. This was an unexpected error which caused a panic.

Okay, allowing abort or continue sounds good as well. Good idea.

This issue is losing momentum. Please help resolve it.