Seems reasonable - how about also modifying the PR check a bit to help guide PR messages? Something like.

Thank you for opening this pull request! Here are some guidelines for writing a good PR message:

- We use the PR message as the default commit message that will be committed to the repository
- We automatically generate the [changelog](...link to changelog) using commits, so please use
  [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) to make this easy:
  - ... examples / specific parts of note
- Writing the perfect PR message is about finding a balance of communicating the problem and
  solution as well as not being too verbose.
- Put yourself in the mindset of the future consumer of this library and what information they need
  to know about this change (it might be very little or nothing beyond the title).
- It's rare that a PR message needs to explain how the change was achieved, and much more
  important to explain the impact on the user, and the rationale for any interesting choices
- If there's info that's useful for reviewing, but not useful for the changelog, move it to followup comment
- If there are changes made to the PR during review, make sure to also update the first PR comment
  (to make it easy to merge)

Perhaps this response should be on every PR?

• We use the PR message as the default commit message that will be committed to the repository
• We automatically generate the [changelog](...link to changelog) using commits, so please use
  Conventional Commits to make this easy:
  • ... examples / specific parts of note

I think this specifically is a good message to put on PRs with non conventional commits titles.

The whole paragraph would make more sense to me in CONTRIBUTING.md or even better: in the PR template (perhaps as some sort of checklist?)

I think a comment with this on every PR is too much, but I'd be keen on putting it for every first-contributor PR.

EDIT: Also this is the matter of another PR imo

EDIT: Also this is the matter of another PR imo

yep

I want another maintainer's opinion on this change before merging it btw.

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (efd1e47) 91.9% compared to head (f6ebea1) 91.9%.
Report is 2 commits behind head on main.

@@          Coverage Diff          @@
##            main    #950    /-   ##
=====================================
  Coverage   91.9%   91.9%           
=====================================
  Files         61      61           
  Lines      15703   15723    20     
=====================================
  Hits       14436   14456    20     
  Misses      1267    1267           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sad to see this go

Every commit on main is made through a PR, internal PR commits don't matter.

What would be great though is to check if the PR title matches the conventional commit style.

yeah, I think we already do that in check-pr.yml

That's right I forgot about that, it's all good then.