Skip to content

docs: recommend Conventional Commits for commits in branches - #59

Closed
AksonovSergei wants to merge 1 commit into
mainfrom
58-recommend-conventional-commits
Closed

AksonovSergei wants to merge 1 commit into
mainfrom
58-recommend-conventional-commits

Conversation

@AksonovSergei

Copy link
Copy Markdown
Member

Closes #58

What and why

CONTRIBUTING.md now recommends the Conventional Commits format for commit messages inside a branch too (step 3 of the workflow and the Pull request title section), so the history of a PR reads the same way as main. It is only a recommendation: CI keeps checking the PR title only, because with Squash and merge the branch commits do not get into main.

Repository settings need a change by a maintainer: they currently allow only Rebase and merge, while CONTRIBUTING.md and pr-rules.yml describe Squash and merge. In Settings → General → Pull Requests: enable Allow squash merging (default message: Pull request title), disable Allow rebase merging.

How it was tested

Documentation only.

  • simulation
  • real robot (overlay or branch image)

Checklist

  • One topic per PR
  • README / docs updated if the behaviour or the usage changed
  • Breaking change (topics, parameters, launch arguments used by applications) is marked with ! in the title

🤖 Generated with Claude Code

CI keeps checking only the PR title, which becomes the squash commit in main.

Refs #58

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AksonovSergei

Copy link
Copy Markdown
Member Author

Moved into #57 (same task, #56).

@AksonovSergei
AksonovSergei deleted the 58-recommend-conventional-commits branch November 9, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: recommend Conventional Commits for commit messages in branches

1 participant