{"id":2584,"date":"2023-01-08T17:42:49","date_gmt":"2023-01-08T20:42:49","guid":{"rendered":"https:\/\/felipeelia.com.br\/?p=2584"},"modified":"2023-01-08T17:49:39","modified_gmt":"2023-01-08T20:49:39","slug":"is-labeling-pull-requests-messages-a-good-idea","status":"publish","type":"post","link":"https:\/\/felipeelia.dev\/is-labeling-pull-requests-messages-a-good-idea\/","title":{"rendered":"Is labeling Pull Requests messages a good idea?"},"content":{"rendered":"\n

Reviewing a Pull Request is always a challenge: how do we keep quality and code consistency while keeping developers motivated? Does labeling Pull Requests messages make things easier to interpret?<\/strong> <\/p>\n\n\n\n

Recently, I tweeted about the https:\/\/conventionalcomments.org\/ website<\/a>. The idea is simple: every time you review a PR, your messages should start with a label<\/strong>, making it clear which is the next expected step (if any.)<\/p>\n\n\n\n

\"\"<\/a>
E a\u00ed, j\u00e1 me segue no Twitter<\/a>?<\/figcaption><\/figure>\n\n\n\n

What is a Pull Request<\/em> (or Merge Request<\/em>?)<\/h2>\n\n\n\n

A Pull Request<\/em> is a request to add some code to the project’s “official” code.<\/strong> Depending on the tool, these requests can be called Merge Requests<\/em>.<\/p>\n\n\n\n

It goes like this:<\/p>\n\n\n\n