diff options
| author | 2025-11-26 19:02:28 -0500 | |
|---|---|---|
| committer | 2025-11-26 19:02:28 -0500 | |
| commit | c62f8376a13e7a4f493167aba1c66a9201fc59c6 (patch) | |
| tree | d58492f972be02c406d26620004e1ffe2086fbc7 /.github/pull_request_template.md | |
| parent | ae103e148eb3c15606b816505492d870ef062ad3 (diff) | |
New upstream version 3.0.0.upstream/3.0.0upstream
Diffstat (limited to '.github/pull_request_template.md')
| -rw-r--r-- | .github/pull_request_template.md | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index a0d7f6e..6e152a1 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,3 +1,21 @@ +<!-- +Thank you for your contribution! + +Please ensure your pull request title follows the Conventional Commits format. +This is important because our release process is automated based on the commit messages. + +Examples: +- feat: Add new feature +- fix: Fix a bug +- docs: Update documentation +- chore: Build process or auxiliary tool changes +- refactor: A code change that neither fixes a bug nor adds a feature +- style: Changes that do not affect the meaning of the code (white-space, formatting, etc) +- test: Adding missing tests or correcting existing tests + +If your change is a breaking change, please add a '!' after the type, e.g., 'feat!: ...' +--> + ### Summary Provide a general description of the code changes in your pull @@ -11,4 +29,4 @@ If there's anything else that's important and relevant to your pull request, mention that information here. This could include benchmarks, or other information. -Thanks for contributing to Roo!
\ No newline at end of file +Thanks for contributing to Roo! |
