First pass at CI and release process improvements #1689
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1689 +/- ##
=======================================
Coverage 79.84% 79.84%
=======================================
Files 197 197
Lines 21767 21792 +25
Branches 4354 4358 +4
=======================================
+ Hits 17379 17399 +20
+ Misses 2234 2232 -2
- Partials 2154 2161 +7
Flags with carried forward coverage won't be shown. Click here to find out more. see 11 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
| change-title-escapes: '\<*_&' # You can add # | ||
|
|
||
| # The template for the name of the draft release | ||
| name-template: 'v$RESOLVED_VERSION 🌈' |
| # default: minor | ||
| # major: | ||
| # labels: | ||
| # - 'feature' |
There was a problem hiding this comment.
why is there a feature and feat label? I know "feat" is super trendy on github right now, but tbh I'd prefer (1) full spelling (2) one way to do things. Is there some reason like tooling requires feats but not features and its out of our hands?
There was a problem hiding this comment.
Nope, we can make the tool handle either feat or feature. I'm a stickler for this kind of thing myself so I get where you're coming from.
There was a problem hiding this comment.
I have this whole section commented out for now, but theoretically it could help guide our semver versioning based on the labels used on PRs that get merged.
…ce" in the auto-generated changelogs
Link the Issue(s) this Pull Request is related to.
Summarize your change.
publishGitHub Action task toPyPI Publish