From bf9feba96a97f75d87941a034f65c9e3e0e146f9 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 6 Apr 2026 19:57:59 +0000
Subject: [PATCH] Fix commit convention: align subject line limit and casing
 with Conventional Commits spec

Agent-Logs-Url: https://github.com/irihitech/Semi.Avalonia/sessions/b699d4e5-4563-449e-b2ba-2c85fce56ca2

Co-authored-by: rabbitism <14807942+rabbitism@users.noreply.github.com>
---
 .github/COMMIT_CONVENTION.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/COMMIT_CONVENTION.md b/.github/COMMIT_CONVENTION.md
index f719e4c..2772e08 100644
--- a/.github/COMMIT_CONVENTION.md
+++ b/.github/COMMIT_CONVENTION.md
@@ -30,10 +30,10 @@ This project follows the [Conventional Commits](https://www.conventionalcommits.
 
 ## Rules
 
-1. **Limit the subject line to 72 characters**
+1. **Limit the subject line to 50 characters** (72 character hard limit)
 2. **Use the imperative mood** in the subject line (e.g., "add feature" not "added feature")
 3. **Do not end the subject line with a period**
-4. **Capitalize the first letter** of the description
+4. **Use lowercase** for the description (e.g., "add feature" not "Add feature")
 5. **Separate subject from body with a blank line**
 6. **Wrap the body at 72 characters**
 7. **Use the body to explain what and why**, not how