Skip to content

Commit af067bb

Browse files
committed
adding pull request template to repo
1 parent d651af4 commit af067bb

1 file changed

Lines changed: 44 additions & 0 deletions

File tree

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
<!--
2+
When creating a PR, be sure to prepend the PR title with the Conventional Commit type (`feat`, `fix`, or `chore`). This is how we manage package versioning and generating CHANGELOG notes.
3+
4+
Examples:
5+
- "feat: add growl notification to spaces:wait"
6+
- "fix: handle special characters in app names"
7+
- "chore: add dist directory to .gitignore"
8+
9+
The expected Conventional Commit types are listed below.
10+
11+
Learn more about [Conventional Commits](https://www.conventionalcommits.org/).
12+
-->
13+
14+
## Summary
15+
<!-- Brief description of the changes in this PR. -->
16+
17+
## Type of Change
18+
### Breaking Changes (major semver update)
19+
- [ ] Add a `!` after your change type to denote a change that breaks current behavior
20+
21+
### Feature Additions (minor semver update)
22+
- [ ] **feat**: Introduces a new feature to the codebase
23+
24+
### Patch Updates (patch semver update)
25+
- [ ] **fix**: Bug fix
26+
- [ ] **deps**: Dependency upgrade
27+
- [ ] **revert**: Revert a previous commit
28+
- [ ] **chore**: Change that does not affect production code
29+
- [ ] **refactor**: Refactoring existing code without changing behavior
30+
- [ ] **test**: Add/update/remove tests
31+
32+
## Testing
33+
**Notes**:
34+
<!-- Add any context/setup necessary for testing. -->
35+
36+
**Steps**:
37+
1. Replace this text with a list of steps used to validate changes or type 'Passing CI suffices'.
38+
2. ...
39+
40+
## Screenshots (if applicable)
41+
42+
## Related Issues
43+
GitHub issue: #[GitHub issue number]
44+
GUS work item: [WI number](WI link)

0 commit comments

Comments
 (0)