5

git add --all && git commit -m "Alright, here's a story for you. I set out to create a navigation mechanism on here, so we could have back buttons and tabs. I also wanted the ability to customise the UI elements. In order to do that, I combined two dependencies. Each one of them provides us with some of the functionalities we need and there's quite a bit of overlap between them. Moreover, each dependency creates the UI elements differently. So customising the UI is becoming a nightmare already, since it's getting harder to tell which one of them is affecting a UI element's appearance. In spite of all that, we have an app that navigates and has tabs."

Comments
  • 1
    Should have been:
    git commit -m "Short story: It works, trust me" -m "" -m "Long Story: ..."

    But I totally understand those kinds of commits.
  • 0
    @T3hbeowulf Can you actually have more than one message on a commit?
  • 1
    @BellAppLab Yep... Chain as many -m "(message)" strings as you want... Each is put on a new line in the commit body.

    The intent is to use the first '-m' for a "50 chars or less" commit title, the second '-m' is empty which acts as a carriage return, and third '-m' to be a detailed message.

    It saves leaving -m "message" off and diving into an editor for the commit.
  • 0
    @T3hbeowulf I didn't know that! That's pretty cool! Thanks!
Add Comment