From 9f9391bc6e5ede1ae7583a47df686ad8ed409d70 Mon Sep 17 00:00:00 2001
From: Aayush_Surana <suranaaayush98@gmail.com>
Date: Fri, 8 Mar 2019 20:01:41 +0530
Subject: [PATCH] Contribution section of README.md updated #510

---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index a3b87d055..67761ed1e 100644
--- a/README.md
+++ b/README.md
@@ -300,6 +300,9 @@ Contributing is easy:
    in the Gitlab UI so we can merge the fix for the next release.
 
 A few guidelines:
+* There should be a short and clear commit message for each merge request.
+* Short and clear title and description are required for each merge request.
+* There should be a short branch name related to the issue, like "update-readme".
 * _No prototypes, please_. Purr Data's biggest strength is that users can
   turn an idea into working code very quickly. But a prototyping language that 
   is itself a prototype isn't very useful. That means Purr Data's core code
-- 
GitLab