|
| 1 | +## Purpose |
| 2 | +<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? --> |
| 3 | +* ... |
| 4 | + |
| 5 | +## Does this introduce a breaking change? |
| 6 | +<!-- Mark one with an "x". --> |
| 7 | + |
| 8 | +- [ ] Yes |
| 9 | +- [ ] No |
| 10 | + |
| 11 | +<!-- Please prefix your PR title with one of the following: |
| 12 | + * `feat`: A new feature |
| 13 | + * `fix`: A bug fix |
| 14 | + * `docs`: Documentation only changes |
| 15 | + * `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
| 16 | + * `refactor`: A code change that neither fixes a bug nor adds a feature |
| 17 | + * `perf`: A code change that improves performance |
| 18 | + * `test`: Adding missing tests or correcting existing tests |
| 19 | + * `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
| 20 | + * `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) |
| 21 | + * `chore`: Other changes that don't modify src or test files |
| 22 | + * `revert`: Reverts a previous commit |
| 23 | + * !: A breaking change is indicated with a `!` after the listed prefixes above, e.g. `feat!`, `fix!`, `refactor!`, etc. |
| 24 | +--> |
| 25 | + |
| 26 | +## Golden Path Validation |
| 27 | +- [ ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors. |
| 28 | + |
| 29 | +## Deployment Validation |
| 30 | +- [ ] I have validated the deployment process successfully and all services are running as expected with this change. |
| 31 | + |
| 32 | +## What to Check |
| 33 | +Verify that the following are valid |
| 34 | +* ... |
| 35 | + |
| 36 | +## Other Information |
| 37 | +<!-- Add any other helpful information that may be needed here. --> |
| 38 | + |
1 | 39 | ## Motivation and Context
|
2 | 40 | <!-- Describe the purpose of the changes being proposed for the Client Advisor module. What problem does it solve or functionality does it add? -->
|
3 | 41 | * ...
|
@@ -33,4 +71,4 @@ Details of documentation updates:
|
33 | 71 |
|
34 | 72 | ## Additional Information
|
35 | 73 | * Any other information that would be helpful for reviewers of the Client Advisor module.
|
36 |
| -* ... |
| 74 | +* ... |
0 commit comments