Dr. Simon Harrer

That’s what I had in mind. Also, with an optional way to fix the error. Basicall all info we would send to the VS Code plugin

Totally agree with your assessment. The thing is the git calls in the code, of which we have a lot. They might fail and stop the program. Having explicit error...

I understand the wish for having a goal that is shared among everybody. Storing shared metadata in git is not that easy. I'd suggest the following: - MVP - Add...

Perhaps there's a middle ground here. We could have errors returned as part of the command methods (start, next, etc.) and when an error happens at a lower level, we...

@hollesse @gregorriegler have a look at the latest commit. I played with panic and a return object.

This is similar to https://github.com/remotemobprogramming/mob/issues/185 so perhaps @lamalex might be interested in this, as well. An alternative would be to use `mob start --feature {branchname}` instead, making it more obvious...

I think this might be the way to go. It enables two functions users asked for. Push a locally created feature branch or create and push a feature branch.

The first `mob start` might require some parameters like `--branch` or `--create`, but the second one can just be `mob start`. Example: ```bash # SCENARIO # Carola main $ mob...

Not sure what you mean. Can you elaborate? Another aspect is on naming: we would now have a `mob start --create` and a `mob start --branch` flag. This feels somewhat...

The first user, in this case Carola, creates the remote branch for feature1. So on Maria's turn, the remote branch has already been pushed. So no need to do any...