From 4727c370d2644826b666ec7303fc8b02eebbdfb4 Mon Sep 17 00:00:00 2001 From: Harald Hoyer Date: Tue, 15 Apr 2025 12:26:10 +0200 Subject: [PATCH] feat: add commit message guidelines - Introduce guidelines for writing commit messages. - Emphasize the use of Conventional Commit format. - Include tips for brevity and clarity in descriptions. --- .copilot-commit-message-instructions.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .copilot-commit-message-instructions.md diff --git a/.copilot-commit-message-instructions.md b/.copilot-commit-message-instructions.md new file mode 100644 index 0000000..e241ef2 --- /dev/null +++ b/.copilot-commit-message-instructions.md @@ -0,0 +1,7 @@ +Use Conventional Commit format. +Avoid overly verbose descriptions or unnecessary details. +Start with a short sentence in imperative form, no more than 50 characters long. +Then leave an empty line and continue with a more detailed explanation. +Write only one sentence for the first part, and two or three sentences at most for the detailed explanation. +Keep message as short as possible. +Use bullet points for multiple changes. \ No newline at end of file