From f7d5b8983f6caeab94585e5359d7de59e7041e9b Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Wed, 24 Jun 2026 08:26:18 +0200 Subject: [PATCH] CONTRIBUTING: discourage Conventional Commits in favor of scope (#6630) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I recently came across this blog post which has put into words how I felt about Conventional Commits for a while. Let’s reference it. --- .github/CONTRIBUTING.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index d5fd3b57..003bb258 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -68,6 +68,9 @@ Here are a few examples for illustration: * Use the `next` branch for developing and sending your pull request. * Use `clang-format` to format your code. * Run the [testsuite](https://i3wm.org/docs/testsuite.html) +* When giving your commit a title, do not use Conventional Commits (“refactor: …”), + instead prefix the commit with the scope of what it changes (“pointer warping: …”): + https://sumnerevans.com/posts/software-engineering/stop-using-conventional-commits/ * If your changes should be reported on the next release's changelog, also add a small single-line file starting with a number (see examples) containing a short explanation of your change either in the