From cde2c55ba8fab37a3c93cbbaec64eef7c1f6ba0f Mon Sep 17 00:00:00 2001 From: Chaim Lev-Ari Date: Wed, 15 Jul 2026 10:32:44 +0300 Subject: [PATCH] docs(guidelines): add git conventions and create-pr skill [BE-13198] (#3160) Co-authored-by: Claude Sonnet 5 --- CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1b70dafc51..059e4247bc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -25,7 +25,7 @@ Each commit message should include a **type**, a **scope** and a **subject**: (): ``` -Lines should not exceed 100 characters. This allows the message to be easier to read on GitHub as well as in various git tools and produces a nice, neat commit log ie: +Lines should not exceed 72 characters. This allows the message to be easier to read on GitHub as well as in various git tools and produces a nice, neat commit log ie: ``` #271 feat(containers): add exposed ports in the containers view @@ -53,6 +53,8 @@ The scope could be anything specifying place of the commit change. For example ` `containers`, `images` etc... You can use the **area** label tag associated on the issue here (for `area/containers` use `containers` as a scope...) +Prefer a single canonical scope per domain to avoid drift, e.g. `kubernetes` (not `k8s`/`kube`), `stacks` (not `stack`), `edgestacks` (not `edgestack`/`edge/stacks`). + ### Subject The subject contains succinct description of the change: