ci: update labels and release drafter #149
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
馃摑 Description
What does this PR do and why is this change necessary?
Updates to use githubs built in release notes and using the following labels.
**NOTE**: The labeler job is dry running on the PR to show what it will do, doesn't execute until we merge.
breaking-change: any changes that break end users or downstream workflows
馃悰 Bug Fixes
bugfix: changes that fix a existing bug
馃殌 New Features
new-feature: changes that add new features such as endpoints or tools
馃挕 Improvements
improvement: changes that improve existing features or reflect small API changes
馃И Testing Improvements
testing: improvements to the testing workflows
鈿欙笍 Repo/CI Improvements
repo-ci-improvement: improvements to the CI workflow, like this PR!
馃摉 Documentation
documentation: updates to the package/repo documentation or wiki
馃摝 Dependency Updates
dependencies: Used by dependabot mostly
Ignore For Release
ignore-for-release: for PRs you dont want rendered in the changelog, usually the release merge to main