From 3ddb618b403e4f3458086fbedc24a5835efb7fd6 Mon Sep 17 00:00:00 2001 From: Ricardo Saraiva Date: Thu, 17 Sep 2026 18:25:14 -0300 Subject: [PATCH] Update README to include Conventional Commits guideline Added a requirement for using Conventional Commits for commit messages. --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cf4604e..9e2679b 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,8 @@ __NOTE:__ The layout will be evaluated, but not strictly against the provided de 1. Create project using any technology of your preference. It’s perfectly OK to use vanilla code or any framework or libraries; 2. Although you can use as many dependencies as you want, you should manage them wisely; 3. It is not necessary to send the notification emails, however, the code required for that would be welcome; -4. The API must be documented in some way. +4. The API must be documented in some way; +5. Use [Conventional Commits](https://www.conventionalcommits.org/) for commit messages throughout the development process; ## Deliverables The project source code and dependencies should be made available in GitHub. Here are the steps you should follow: