Closed tamalCodes closed 1 year ago
To reduce notifications, issues are locked. Your issue will be unlocked when we add the label, 🚀 ready
.
Hi @tamalCodes, you may start working on this?
Hi @tamalCodes, you may start working on this?
@tamalCodes, check this out: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
Description
I saw that previously we closed #833 which was meant to add this feature up, and we also do have #866 which is also almost the same though having a changelog is somewhat different than having semantic releases scheduled with time.
Here's what I offer. We can use Release Drafter, a popular Opensource action that automatically creates Draft releases for you, along with proper semantic versioning.
How it works ?
.github/workflows/release-drafter.yml
which will be responsible for drafting your releases based on the branches..github/release-drafter.yml
which will contain a template file and it will decide how the versioning is based upon labelsbug
,feature
and so on.Workflow and Demo
If you wish for a demo, head over to Milan's Releases where we draft a release along with proper release notes as soon as we squash-merge a change to the
beta
branch. We do publish a release every week when we merge ourbeta
branch to themain
branch.It is fully based on the labels I add to the PR. If I add a
bug
it will be considered apatch
, forfeature
it goes under theminor
changes, and so on. Learn more about Semantic versioning hereScreenshots
This is how draft changes looks like 👇🏻
This is how published changes looks like 👇🏻
Checklist