Platform Engineering Lead @hashnode | Serverless and Frontend Enthusiast
Platform Engineering Lead @hashnode Serverless and Frontend Enthusiast π€ Into AWS, TypeScript, React, Svelte and upcoming trendsβ¦ βοΈ AWS Community Builder Serverless Coding is not only a job β it's a passion. Based in Hamburg π©πͺ
Markdown supported Β· ββ΅ to post
This article provides a great detailed explanation to get familiar with the subject. Thank you!
I'm migrating circleci pipelines to github actions because I was mixing then to get more github events triggering the pipelines in circleci and it was geting complicated. I start paying for github anyway so I want to keep everything in one place. Was thinking on ways to integrate the tag and releases feature in a pipeline with staging and production env, and your article give me a good starting point. Thanks for sharing, good points for new comes in github actions and experienced in other ci/cd
The environment property is amazing, I didn't know about it yet and I already know it will deprecate a lot of glue code. Thanks for sharing, Jannik :)
Jannik Wempe
Mathieu Lemaire
Hello there - thank you very much for the detailed steps π―. Applied this on my repo (the manual steps with draft releases) but now I am facing a purist issue: how do you deal with draft releases that never get published?