From 9a13b07f6ae94dd62b4b2224eb3cd3ea2830844b Mon Sep 17 00:00:00 2001 From: Sandrine Bailleux Date: Tue, 3 May 2022 08:14:23 +0200 Subject: [PATCH] build(commitlint): make the scope optional In all TF-A commit messages, the first line must comply to the following format: type(scope): description Although the conventional commits specification says that the scope above is optional, we have made it mandatory in TF-A and the following error message is printed if no scope is provided: scope may not be empty [scope-empty] However, this can be too restrictive for some types of commits. For example, it is typically hard to choose a scope for documentation patches which modify several documents of different natures. Lift this restriction in the tools and leave it up to the developer to decide whether a scope is needed or not. Change-Id: I9d35e7790fc3fa74651794216fe8db265ad09982 Signed-off-by: Sandrine Bailleux --- .commitlintrc.js | 1 - 1 file changed, 1 deletion(-) diff --git a/.commitlintrc.js b/.commitlintrc.js index ed971a365..cfafbedc2 100644 --- a/.commitlintrc.js +++ b/.commitlintrc.js @@ -68,7 +68,6 @@ module.exports = { "type-enum": [2, "always", types], /* Error */ "scope-case": [2, "always", "lower-case"], /* Error */ - "scope-empty": [2, "never"], /* Error */ "scope-enum": [1, "always", scopes] /* Warning */ }, };