Commit / PR naming conventions for

Now that we have vanilla components, React components, and elements… many packages… how can our PRs use conventional commit syntax to generate package-specific changelogs?

E.g. I’m using the @carbon/react package for all React core components. How do I see what’s new?

E.g. I’m just using @carbon/button-react package, how can I see what’s new in each release?

Acceptance criteria:

• Consistent commit and PR naming for all packages
• Just root-level package Husky config or however we enforce conventional commit messages
• Document this in /docs

P.S. I wonder if we should pull “contributing” content (syntax style, commit messages, sassdoc annotation style, etc) out of the .github directory and into /docs because the docs directory is much more discoverable.

[kinueng]

Could we add the PR/commit convention to a CONTRIBUTING.md file in carbon instead of the docs/developing.md?

The CONTRIBUTING.md has a step[1] that mentions briefly the commit message convention.

[1] https://github.com/carbon-design-system/carbon/blob/master/.github/CONTRIBUTING.md#8-make-a-pull-request

[stale[bot]]

As there’s been no activity since this issue was marked as stale, we are auto-closing it.