git-conventions

Standardize git commit messages and branch naming by enforcing conventional commit structures and a type/name branch pattern. This establishes required formats, examples, and guardrails to ensure uniform version control practices across all team repositories.

The conventional commit format for pull request titles requires a descriptive, type-prefixed structure. This ensures easier review by clearly indicating the nature of the changes, aligning PR discussions with overall workflow conventions.

Enforcing conventional commits improves traceability by aligning commit types and branch names with a standardized format. This consistency enables automation readiness, allowing teams to generate changelogs and release notes directly from commit history.

These git conventions apply specifically to rloisell/ and bcgov-c/ repositories. They establish standard branch naming, commit message formats, and PR discussion guidelines to enforce consistent Git workflows across those specific repository environments.

You need a type/name branch naming pattern, such as feat/login or fix/payment-bug, before writing conventional commit messages. This standardizes the workflow from branch creation through commit and pull request review.

Automating changelog generation from commit history requires strict adherence to conventional commit message formats and branch naming conventions. Without uniformity and quality in these version control practices, automated release notes and changelogs will be incomplete or inaccurate.