Please, paint new branch errors in RED (or any visible color)
- From
- Jose Wielandt <jose.wielandt@timining.com>
- Date
- Dec 10, 2021, 11:36 UTC
- Message-ID
- <CAJrA3nLUG_m1ftdAyzFBkmL3m1vMPuv5dd3bYVVOmXV-fThwnA@mail.gmail.com>
Hi community,
At my work we've been struggling a lot with not realizing that our new branch creation actually failed, ending up with a push directly to develop. What are those cases?
$ git checkout -b feature/solve p-eq-np fatal: Cannot update paths and switch to branch 'feature/solve' at the same time.
What's my proposal?
$ git checkout -b feature/solve p-eq-np ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
FATAL: CANNOT UPDATE PATHS AND SWITCH TO BRANCH 'feature/solve' AT THE SAME TIME
YOU STILL IN THE SAME BRANCH ! ! ! !
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
***(but in bright RED)***
Another case!
$ git branch feature/solve p-eq-np fatal: Not a valid object name: 'p-eq-np'.
I'll let that one to your imagination but please, make it appear in red so we can easily (visually) realize that something went wrong.
This has been the third time in a month we accidentally pushed changes to develop bc we didn't realize that the command failed.
Thanks!