Closed ZibanPirate closed 2 years ago
@ZibanPirate why don't you guys use semantic-release ? it works with react/next, and i guess everything related to js/ts I can implement it if needed
@ZibanPirate why don't you guys use semantic-release ? it works with react/next, and i guess everything related to js/ts
I can implement it if needed
That's a good idea, however, since this project is open-source, we really don't want anything to get in the way of a new contributor to fork/clone/commit/push changes, having semantic-release will enforce some practices that not everyone knows about or want.
That been said, if you disagree or maybe know other use cases of it that do not enforce practice but rather add to the experience, please let us know
Is your feature request related to a problem? Please describe. Currently we're writing release notes manually, tagging each PR and contributor included in that release, eg: stg-v2.14.0 and v2.7.1
Describe the solution you'd like Using Github automated release notes, when we draft a release, all the changes will be populated automatically, we still need to do manual adjustment, but mostly minor ones.
Describe alternatives you've considered Maybe search the Github Actions marketplace for third-party alternatives