Commits are hard

Commit messages can be a heated topic among engineers, although not as controversial as spaces vs tabs.

At Jellyvision, we use Atlassian products for our project and code management, and gitflow for branch management. This means, we can link our code directly to our user stories and defects. 

Using branch names like:

  • feature/JIRA-TICKET/briefDescription
  • bugfix/JIRA-TICKET/briefDescription
  • patch/JIRA-TICKET/briefDescription
  • develop
  • release

…and commit messages like: “Present-tense-verb description of code changes – TICKET-ID”

Allow our systems to integrate together:

Bitbucket Integration

JIRA Integration

When you use smart commit messages and branch names, Bitbucket and JIRA can automatically integrate together

But, We’re not perfect

Even the best developers make bad commit messages. Whether from lack of sleep, lack of time, or just for the fun of beating oneself up over tiny syntax errors, Jellyvision engineers can be guilty of “non-helpful” commit messages.

Below are some commit messages that make it into our Commit Message Hall of ShameTM:

  • “Bad Assumptions”
  • “yolo ton of cert verify”
  • “need self yos”
  • “Finally”
  • “WHOA”
  • “”
  • “fix”
  • “What is going on PHP?”
  • “level up!”
  • “Badger badger badger”
  • “jkjk lol. nevermind. we still want that dropdown”
  • “bad bad bad bad bad bad bad yolo no params in view”
  • “git stash %^&$ up”
  • “oops”

Related Articles

Tagged with: