-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
3240a86
commit 6e37d43
Showing
1 changed file
with
37 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
## Purpose | ||
<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? --> | ||
* ... | ||
|
||
## Does this introduce a breaking change? | ||
<!-- Mark one with an "x". --> | ||
|
||
- [ ] Yes | ||
- [ ] No | ||
|
||
<!-- Please prefix your PR title with one of the following: | ||
* `feat`: A new feature | ||
* `fix`: A bug fix | ||
* `docs`: Documentation only changes | ||
* `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) | ||
* `refactor`: A code change that neither fixes a bug nor adds a feature | ||
* `perf`: A code change that improves performance | ||
* `test`: Adding missing tests or correcting existing tests | ||
* `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) | ||
* `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) | ||
* `chore`: Other changes that don't modify src or test files | ||
* `revert`: Reverts a previous commit | ||
* !: A breaking change is indicated with a `!` after the listed prefixes above, e.g. `feat!`, `fix!`, `refactor!`, etc. | ||
--> | ||
|
||
## Golden Path Validation | ||
- [ ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors. | ||
|
||
## Deployment Validation | ||
- [ ] I have validated the deployment process successfully and all services are running as expected with this change. | ||
|
||
## What to Check | ||
Verify that the following are valid | ||
* ... | ||
|
||
## Other Information | ||
<!-- Add any other helpful information that may be needed here. --> |