Magic Release Notes — Neciu Dan
Just merge your PRs without worrying about release notes. Let GitHub Actions do the work for you by creating a Draft Release and then push to production by clicking a button and get notified on Slack.
We used to have a small annoying problem in my company. I call it small-annoying because it was small enough not to deserve allocated resources to solve, but it was annoying enough to bother me every couple of weeks.
We have a Frontend React Application that communicates to a backend API, a gateway to multiple services, and one main monolithic application.
You need to do a production release; you last did one about ten days ago, and now that the stars have aligned, you have the perfect window to press the button.
And here you can see how annoying this was for me. As I usually was in charge of pushing the deploy button, I had to ensure everything in line to be released was tested, verified, and given the green light to be deployed.
First, I check the status of JIRA tickets for Ready for Release and write down the ticket number and title. Then, I go commit by commit in the Frontend React Application, note the JIRA tickets in the title, write them down, and do the same for our Backend Go Application and other services.
