git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Please, paint new branch errors in RED (or any visible color)

From
JWJose 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!
Next: Ævar Arnfjörð Bjarmason
Message 1 of 8 in “Please, paint new branch errors in RED (or any visible color)”
  1. Jose WielandtDec 10, 2021
  2. Ævar Arnfjörð BjarmasonDec 10, 2021
  3. Fabian StelzerDec 10, 2021
  4. Jose WielandtDec 10, 2021
  5. Ævar Arnfjörð BjarmasonDec 11, 2021
  6. Junio C HamanoDec 12, 2021
  7. Ævar Arnfjörð BjarmasonDec 12, 2021
  8. Eric SunshineDec 12, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.