chore: update pull request template (#5123)

tmorehouse · web-flow · commit 1c8014a35c91 · 2020-04-13T18:04:25.000-03:00
Co-authored-by: Jacob Müller
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -8,32 +8,33 @@ A clear and concise description of what the pull request does.
 
 **What kind of change does this PR introduce?** (check at least one)
 
-- [ ] Bugfix
-- [ ] Feature
-- [ ] Enhancement
-- [ ] ARIA accessibility
-- [ ] Documentation update
+- [ ] Bugfix (fixes a boo-boo in the code) - `fix(...)`, requires a patch version update
+- [ ] Feature (adds a new feature to BootstrapVue) - `feat(...)`, requires a minor version update
+- [ ] Enhancement (augments an existing feature) - `feat(...)`, requires a minor version update
+- [ ] ARIA accessibility (fixes or improves ARIA accessibility) - `fix(...)`, requires a patch or minor version update
+- [ ] Documentation update (improves documentation or typo fixes) - `chore(docs)`, requires a patch version update
 - [ ] Other (please describe)
 
 **Does this PR introduce a breaking change?** (check one)
 
 - [ ] No
-- [ ] Yes (please describe)
+- [ ] Yes (please describe since breaking changes require a minor version update)
 
 **The PR fulfills these requirements:**
 
 - [ ] It's submitted to the `dev` branch, **not** the `master` branch
 - [ ] When resolving a specific issue, it's referenced in the PR's title (i.e. `[...] (fixes #xxx[,#xxx])`, where "xxx" is the issue number)
 - [ ] It should address only one issue or feature. If adding multiple features or fixing a bug and adding a new feature, break them into separate PRs if at all possible.
-- [ ] The title should follow the [**Conventional Commits**](https://www.conventionalcommits.org/) naming convention (i.e. `fix(alert): not alerting during SSR render`, `docs(badge): update pill examples`, `chore(docs): fix typo in README`, etc). **This is very important, as the `CHANGELOG` is generated from these messages.**
+- [ ] The title should follow the [**Conventional Commits**](https://www.conventionalcommits.org/) naming convention (i.e. `fix(alert): not alerting during SSR render`, `docs(badge): update pill examples`, `chore(docs): fix typo in README`, etc). **This is very important, as the `CHANGELOG` is generated from these messages, and determines the next version type (patch or minor).**
 
 **If new features/enhancement/fixes are added or changed:**
 
-- [ ] Includes documentation updates (including updating the component's `package.json` for slot and event changes)
+- [ ] Includes documentation updates
+- [ ] Includes component package.json meta section updates (prop, slot and event changes/updates)
 - [ ] Includes any needed TypeScript declaration file updates
-- [ ] New/updated tests are included and passing (if required)
+- [ ] New/updated tests are included and passing (required for new features and enhancements)
 - [ ] Existing test suites are passing
-- [ ] CodeCov for patch has met target
+- [ ] CodeCov for patch has met target (all changes/updates have been tested)
 - [ ] The changes have not impacted the functionality of other components or directives
 - [ ] ARIA Accessibility has been taken into consideration (Does it affect screen reader users or keyboard only users? Clickable items should be in the tab index, etc.)
 
