In this PR i will remove this empty commit when doing mob start as this can lead to branches where someone did a mob start and did not work there and after few weeks we revisit the project and do mob start and do not notice that this is a running session with just the empty commit.
The main reason for this empty commit was optimization of ci runs. We could again introduce the ci.skip push option and give the user the option to either disable it or to explicitly enable it. I think in the most cases this should not make any problems and could be held that we have a option to disable the option.
The CI skip options would for example not work on github, but should not be any issue adding the option there. It just will not skip the ci. This is something which hurts less than the empty commit.
In this PR i will remove this empty commit when doing mob start as this can lead to branches where someone did a mob start and did not work there and after few weeks we revisit the project and do mob start and do not notice that this is a running session with just the empty commit.
The main reason for this empty commit was optimization of ci runs. We could again introduce the ci.skip push option and give the user the option to either disable it or to explicitly enable it. I think in the most cases this should not make any problems and could be held that we have a option to disable the option.
The CI skip options would for example not work on github, but should not be any issue adding the option there. It just will not skip the ci. This is something which hurts less than the empty commit.
closes #408