From c09bd411d2d947eda64f5a92a0658f7640c3836f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20de=20la=20Pe=C3=B1a?= Date: Wed, 11 Dec 2024 07:44:11 +0100 Subject: [PATCH] docs: remove breaking from the contributing guide --- docs/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing.md b/docs/contributing.md index 63bd033df4..5bc9802e4f 100644 --- a/docs/contributing.md +++ b/docs/contributing.md @@ -29,7 +29,7 @@ Please just be sure to: * follow the style, naming and structure conventions of the rest of the project. * make commits atomic and easy to merge. * use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) for the PR title. This will help us to understand the nature of the changes, and to generate the changelog after all the commits in the PR are squashed. - * Please use the `break` type for breaking changes, as these categories are considered as `breaking change` in the changelog. + * Please use the `feat!`, `chore!`, `fix!`... types for breaking changes, as these categories are considered as `breaking change` in the changelog. Please use the `!` to denote a breaking change. * Please use the `security` type for security fixes, as these categories are considered as `security` in the changelog. * Please use the `feat` type for new features, as these categories are considered as `feature` in the changelog. * Please use the `fix` type for bug fixes, as these categories are considered as `bug` in the changelog.