search

RADAR-base / RADAR-Kubernetes

Kubernetes deployment of RADAR-base
Apache License 2.0
17 stars 9 forks source link

Use Release Drafter Github action #222

Closed keyvaann closed 1 year ago

keyvaann commented 2 years ago

Using a tool like this should help us to make more informative releases. https://github.com/marketplace/actions/release-drafter

blootsvoets commented 2 years ago

Note that Github already offers something similar with the Generate release notes button. If you want, I can do that for 1.0.0?

blootsvoets commented 2 years ago

I've done the Github release notes generator for 1.0.0: https://github.com/RADAR-base/RADAR-Kubernetes/releases/tag/v1.0.0.

I see added value to release drafter if we start very carefully labelling PRs (major, minor, patch, enhancement, bug) or use autolabeler and carefully name our branch names (fix/something, feature/something).

If you agree, could you please edit the PR template to be less verbose and mention these labels, as well as creating the labels? The readme should then contain in contribution guidelines what the branch names should be.

keyvaann commented 1 year ago

Thanks, I think the release info that Github provides is should be good enough, and we probably don't elaboracy of the tool I shared. Requiring more information for PRs can discourage contribution especially that there isn't many of them. I agree with changing PR format, it's already difficult for me to use that. Maybe we can squash PRs into one commit to make release notes more readable.