This page serves as a guide for some aspects of code management, in this way, our repository will be cohesive and homogeneous.

We will follow the standard Conventional Commits. It allows a clear and quick way of writing a commit message. The structure is the following:

<type>: <description>

[optional body]

[optional footer(s)]

The type keyword can be:

• fix: a commit to patch a bug in the code.
• feat: a commit that introduces a new feature to the code.
• test: if we add or fix tests.
• ci: the change affects configuration files and scripts related to continuous integration.
• chore: routine tasks that are not specific to a feature or bug such as adding content to the .gitignore file or installing a dependency.
• docs: when only documentation is modified.

Any type of branch must always be linked with an existing issue.

Any new feature-inducing branches must always be created from develop. The naming convention will be the following:

feature/<task-issue-number>-<task-name>

For example, let's say there needs to be a new branch from issue #9 called "Crud usuarios", then the name should be something like feature/9-users.

The other type of branch would be a hotfix branch, created when a bug needs to be fixed. The naming convention will be the following:

hotfix/<bug-issue-number>-<bug-name>