Commit Graph
2 Commits
Author SHA1 Message Date
Esa Kataja 0d01f6e8dd docs: use release: for squash-merged release pull requests
A release spans a fix, a feature and some chores at once, so no single
conventional type describes it honestly. release: makes main's log one line
per deployment, which is what that branch is for, with the pull request body
as the notes.
2026-09-06 00:01:25 +03:00
Esa Kataja b9e0d8d65d docs: add CONTRIBUTING and adopt Conventional Commits
A dozen conventions had accumulated that existed only in my head and in the
commit log: Finnish interface against English code, no infrastructure detail
in the repository, migrations immutable once shipped, interactions that patch
rather than navigate, ponytail comments marking deliberate shortcuts, and
asserting what a response does rather than only that it responded — the one
that let the /ruoat 404 ship.

Commit messages take a type from here on: feat, fix, chore and the rest. The
body still carries the weight, since these commits are the only design record
this project has. Pull request titles get the same treatment, because main is
squash-merged and a title becomes a commit message on it.
2026-09-05 23:59:22 +03:00