Are you using any Github Marketplace App/Action or have you written your own pipeline or are you using something entirely different?
Let's discuss (* - *)...
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Edition 3 — Monday Memes
Sukhpinder Singh -
Lucia Auth is getting deprected
Gleb Kotovsky -
Multi-Agent System for 🚀 ANY AI/ML Model: 🌐 Web Scraping & 📝 Content Analysis Powered by the 🔗 AI/ML API
Jad Tounsi -
🚀 pgai Vectorizer: Automate AI Embeddings With One SQL Command in PostgreSQL
Avthar Sewrathan -
Top comments (4)
We used to create releases directly on Github manually following the semver guidelines: semver.org/
We did this because it was a more controlled deployment process and because our pipelines were external (using Concourse), it gave us a hook/event to start the build off of
We (GrimoireLab project) have created our own pipeline for creating releases. You can check the whole workflow here, https://github.com/vchrombie/release-....
We created Bitergia/release-tools for creating, managing the changelog notes and we have github action workflows or publishing and automation work.
Currently using semantic-release for versioning and generating release notes semantic-release.gitbook.io/semant...
Will check it out (-.-)