homelab/portainer
1
0
Fork 0
mirror of https://github.com/portainer/portainer.git synced 2026-08-07 10:04:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs(guidelines): add git conventions and create-pr skill [BE-13198] (#3160)

Browse Source 
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Chaim Lev-Ari
2026-07-15 10:32:44 +03:00
committed by GitHub
parent b485de295b
commit cde2c55ba8
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+3 -1
View File
@@ -25,7 +25,7 @@ Each commit message should include a **type**, a **scope** and a **subject**:
<type>(<scope>): <subject> <type>(<scope>): <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 #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... `containers`, `images` etc...
You can use the **area** label tag associated on the issue here (for `area/containers` use `containers` as a scope...) 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 ### Subject
The subject contains succinct description of the change: The subject contains succinct description of the change: