cloud/music_library
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update commit message conventions for dependencies

Browse Source
This commit is contained in:
Claudio Ortolina
2026-04-28 22:46:09 +01:00
parent 5656db609a
commit 83ebfb7961
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/project-conventions.md
+1
View File
@@ -9,6 +9,7 @@ Rules extracted from commit history that are specific to this project and not al
- Reverts use `Revert "Original message"` convention - Reverts use `Revert "Original message"` convention
- NEVER ADD a "Co-Authored-By" reference in the message body - NEVER ADD a "Co-Authored-By" reference in the message body
- **When the work maps to a Backlog.md task, prefix the commit subject with the task identifier**, e.g. `ML-3: fix scrobble rule ordering`. The prefix counts toward the 60-character limit. - **When the work maps to a Backlog.md task, prefix the commit subject with the task identifier**, e.g. `ML-3: fix scrobble rule ordering`. The prefix counts toward the 60-character limit.
- **Dependency updates use `Update dependencies` for mix and `Update npm dependencies` for npm.** The subject describes the intent, not the mechanics — never use "bump". List each specific version change in the commit body as `package_name from => to`.
## Workflow ## Workflow