core-pr-helper

To generate a branch name and PR description for a Calimero core pull request, use an automation tool that outputs a single standards-compliant branch name and a structured PR body. This ensures your pull request follows repository conventions for type, scope, and summary formatting.

A Calimero core branch name should follow the type-scope-short-summary pattern. This naming convention ensures consistency across pull requests by clearly identifying the commit type, the affected scope, and a brief summary of the code changes.

A Calimero core PR description template requires four specific sections: Title, Description, Test plan, and Documentation update. Including these sections ensures the pull request provides comprehensive context and verification steps for code reviewers.

You need to use a standardized PR template for code review when creating a Calimero core PR or making any core-related change. Applying this template ensures your pull request meets repository standards and provides necessary documentation updates.

No, the generation process produces exactly one branch name following the type-scope-short-summary pattern. This single-branch name generation approach ensures strict adherence to repository conventions without offering alternative naming options.

Yes, the PR description generator includes a dedicated Test plan section. This section is a mandatory part of the PR body template, ensuring that all code changes are accompanied by clear verification steps for reviewers.