Skip to content

docs(contributing): the PR title is the whole commit; fixing a release entry (#289) - #322

Merged
mottihoresh merged 1 commit into
mainfrom
docs/release-entry-fix-289
Oct 1, 2026
Merged

mottihoresh merged 1 commit into
mainfrom
docs/release-entry-fix-289

Conversation

@mottihoresh

Copy link
Copy Markdown
Collaborator

Follow-up to the release setup (#289 / #316).

What happened: #318's squash commit carried its whole PR description. One line of it, a wrapped C++ signature starting DrumDisplay(, made release-please's Conventional Commits parser fail (unexpected token), so it silently dropped the feat(firmware) and no release PR appeared. It was fixed with a BEGIN_COMMIT_OVERRIDE block on #318 plus a manual Release run, which produced #321 (release firmware 0.2.0).

Prevention:

  • Repo setting (done separately): squash commits default to the PR title only, so descriptions are never parsed.
  • This PR, docs/contributing/conventions.md:
    • says the PR title is the whole commit on main for both firmware and hardware, and that descriptions can hold any code;
    • adds Fixing a release entry: the override block, then re-run the Release workflow.

Verification: check_doc_refs.py passes; whitespace clean.

…e entry (#289)

- The squash commit on main is the PR title only, so the description is
  never parsed: write it freely, code included.
- How to repair a missed or wrong changelog entry: a
  BEGIN_COMMIT_OVERRIDE block in the merged PR's description, then re-run
  the Release workflow. Used for #318, whose description a code line made
  unparseable.
@mottihoresh mottihoresh added the docs Documentation site content label Oct 1, 2026
@mottihoresh
mottihoresh merged commit fa2e8ea into main Oct 1, 2026
9 checks passed
@mottihoresh
mottihoresh deleted the docs/release-entry-fix-289 branch October 1, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation site content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant