|
6 | 6 | [](https://github.com/main-branch/create_github_release/actions/workflows/continuous_integration.yml) |
7 | 7 | [](https://codeclimate.com/github/main-branch/create_github_release/maintainability) |
8 | 8 | [](https://codeclimate.com/github/main-branch/create_github_release/test_coverage) |
| 9 | +[](https://conventionalcommits.org) |
9 | 11 | [](https://main-branch.slack.com/archives/C07NG282N80) |
10 | 12 |
|
11 | 13 | When run in your gem's git worktree, the `create-github-release` script does the |
@@ -40,6 +42,8 @@ Tested on Ruby 3.0+ |
40 | 42 | * [How is the changelog updated?](#how-is-the-changelog-updated) |
41 | 43 | * [Development](#development) |
42 | 44 | * [Contributing](#contributing) |
| 45 | + * [Commit message guidelines](#commit-message-guidelines) |
| 46 | + * [Pull request guidelines](#pull-request-guidelines) |
43 | 47 | * [License](#license) |
44 | 48 |
|
45 | 49 | ## Installation |
@@ -401,6 +405,31 @@ To install this gem onto your current Ruby environment, run `bundle exec rake in |
401 | 405 | Bug reports and pull requests are welcome on |
402 | 406 | [this project's GitHub page](https://github.com/main-branch/create_github_release) |
403 | 407 |
|
| 408 | +### Commit message guidelines |
| 409 | + |
| 410 | +All commit messages must follow the [Conventional Commits |
| 411 | +standard](https://www.conventionalcommits.org/en/v1.0.0/). This helps us maintain a |
| 412 | +clear and structured commit history, automate versioning, and generate changelogs |
| 413 | +effectively. |
| 414 | + |
| 415 | +To ensure compliance, this project includes: |
| 416 | + |
| 417 | +* A git commit-msg hook that validates your commit messages before they are accepted. |
| 418 | + |
| 419 | + To activate the hook, you must have node installed and run `npm install`. |
| 420 | + |
| 421 | +* A GitHub Actions workflow that will enforce the Conventional Commit standard as |
| 422 | + part of the continuous integration pipeline. |
| 423 | + |
| 424 | + Any commit message that does not conform to the Conventional Commits standard will |
| 425 | + cause the workflow to fail and not allow the PR to be merged. |
| 426 | + |
| 427 | +### Pull request guidelines |
| 428 | + |
| 429 | +All pull requests must be merged using rebase merges. This ensures that commit |
| 430 | +messages from the feature branch are preserved in the release branch, keeping the |
| 431 | +history clean and meaningful. |
| 432 | + |
404 | 433 | ## License |
405 | 434 |
|
406 | 435 | The gem is available as open source under the terms of the |
|
0 commit comments