|
| 1 | +<!-- |
| 2 | + Copyright 2026 UCP Authors |
| 3 | +
|
| 4 | + Licensed under the Apache License, Version 2.0 (the "License"); |
| 5 | + you may not use this file except in compliance with the License. |
| 6 | + You may obtain a copy of the License at |
| 7 | +
|
| 8 | + http://www.apache.org/licenses/LICENSE-2.0 |
| 9 | +
|
| 10 | + Unless required by applicable law or agreed to in writing, software |
| 11 | + distributed under the License is distributed on an "AS IS" BASIS, |
| 12 | + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 13 | + See the License for the specific language governing permissions and |
| 14 | + limitations under the License. |
| 15 | +--> |
| 16 | + |
| 17 | +# Description |
| 18 | + |
| 19 | +Please include a summary of the changes and the related issue. Please also |
| 20 | +include relevant motivation and context. |
| 21 | + |
| 22 | +## Type of change |
| 23 | + |
| 24 | +Please delete options that are not relevant. |
| 25 | + |
| 26 | +- [ ] Bug fix (non-breaking change which fixes an issue) |
| 27 | +- [ ] New feature (non-breaking change which adds functionality) |
| 28 | +- [ ] **Breaking change** (fix or feature that would cause existing |
| 29 | + functionality to not work as expected, **including removal of schema files |
| 30 | + or fields**) |
| 31 | +- [ ] Documentation update |
| 32 | + |
| 33 | +--- |
| 34 | + |
| 35 | +### Is this a Breaking Change or Removal? |
| 36 | + |
| 37 | +If you checked "Breaking change" above, or if you are removing **any** schema |
| 38 | +files or fields: |
| 39 | + |
| 40 | +- [ ] **I have added `!` to my PR title** (e.g., `feat!: remove field`). |
| 41 | +- [ ] **I have added justification below.** |
| 42 | + |
| 43 | +## Breaking Changes / Removal Justification |
| 44 | + |
| 45 | +(Please provide a detailed technical and strategic rationale here for why this |
| 46 | +breaking change or removal is necessary.) |
| 47 | + |
| 48 | +--- |
| 49 | + |
| 50 | +## Checklist |
| 51 | + |
| 52 | +- [ ] My code follows the style guidelines of this project |
| 53 | +- [ ] I have performed a self-review of my own code |
| 54 | +- [ ] I have commented my code, particularly in hard-to-understand areas |
| 55 | +- [ ] I have made corresponding changes to the documentation |
| 56 | +- [ ] My changes generate no new warnings |
| 57 | +- [ ] I have added tests that prove my fix is effective or that my feature works |
| 58 | +- [ ] New and existing unit tests pass locally with my changes |
| 59 | +- [ ] Any dependent changes have been merged and published in downstream modules |
| 60 | + |
| 61 | +--- |
| 62 | + |
| 63 | +### Pull Request Title |
| 64 | + |
| 65 | +This repository enforces **Conventional Commits**. Your PR title must follow |
| 66 | +this format: `type: description` or `type!: description` for breaking changes. |
| 67 | + |
| 68 | +**Types:** |
| 69 | + |
| 70 | +- `feat`: A new feature |
| 71 | +- `fix`: A bug fix |
| 72 | +- `docs`: Documentation only changes |
| 73 | +- `style`: Changes that do not affect the meaning of the code (white-space, |
| 74 | + formatting, etc) |
| 75 | +- `refactor`: A code change that neither fixes a bug nor adds a feature |
| 76 | +- `perf`: A code change that improves performance |
| 77 | +- `test`: Adding missing tests or correcting existing tests |
| 78 | +- `chore`: Changes to the build process or auxiliary tools and libraries |
| 79 | + |
| 80 | +**Breaking Changes:** |
| 81 | + |
| 82 | +If your change is a breaking change (e.g., removing a field or file), you |
| 83 | +**must** add `!` before the colon in your title: |
| 84 | +`type!: description` |
| 85 | + |
| 86 | +**Examples:** |
| 87 | + |
| 88 | +- `feat: add new payment gateway` |
| 89 | +- `fix: resolve crash on checkout` |
| 90 | +- `docs: update setup guide` |
| 91 | +- `feat!: remove deprecated buyer field from checkout` |
0 commit comments