Skip to content

feat(challenge): Update README to include Conventional Commits guideline #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ricardosaraiva merged 1 commit into from
Sep 18, 2026
+2 −1
Merged

feat(challenge): Update README to include Conventional Commits guideline #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down