You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
+
-[ ]**perf**: Performance improvement
27
+
-[ ]**deps**: Dependency upgrade
28
+
-[ ]**revert**: Revert a previous commit
29
+
-[ ]**docs**: Documentation change
30
+
-[ ]**style**: Styling update
31
+
-[ ]**chore**: Change that does not affect production code
32
+
-[ ]**refactor**: Refactoring existing code without changing behavior
0 commit comments