There are 6 repositories under release-management topic.
Repo for SIG release
Pause your GitHub Actions workflow and request manual approval from set approvers before continuing
changes automates python library release tasks.
Your buddy in managing and maintaining GitHub repositories, and releases. Automatically generate changelogs from issues and merged pull-requests.
Simple Github release command line tool
Automatically bump Homebrew formula after a release
Release coordination and deployment platform, just for your mobile apps
Opinionated CLI for continuous delivery of npm packages
A zero-configuration release automation tool for Node packages inspired by create-react-app and Travis CI.
Command line tool for releasing new versions of a project
Strongly opinionated python project management.
DevOps tool for managing microservices
abstract_feature_branch is a Ruby gem that provides a variation on the Branch by Abstraction Pattern by Paul Hammant and the Feature Toggles Pattern by Martin Fowler (aka Feature Flags) to enable Continuous Integration and Trunk-Based Development.
Poetry plugin for easy release management
🚀 Continuous Delivery and Orchestration as code for Elixir
⛳️ PASS: ITIL 4 Foundation (IT Service Management) by learning based on our Questions & Answers (Q&A) Practice Tests Exams.
Stop wrestling with code dependencies. Use Codependence! 🤼‍♀️
:neckbeard::tada: Command line interface for managing release notes. :tada::neckbeard:
Simple and clear project management tool. With which it is possible to display one or more projects graphically.
Automates versioning and release management
Automatically publish an existing Draft Release when the "package.json" version changes
orcharhino is THE tool to automatically deploy in a datacenter server, perform configuration management, and always be up-2-date using patch management.
A GitHub Action to list merged pull requests on the source branch when a PR is created
Functions Continous Deployment demo (using VSTS)
find commits in a GitHub repository that got added after the most recent release/tag
GitHub integration which validates release note/change log updates occur