We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluster hasn't had a release yet, which we will need to start doing to package it for pypi and Debian.
The proposal is the use to use Conventional Commit Messages in combination with the following github action https://github.com/google-github-actions/release-please-action to automate all the release process.
The text was updated successfully, but these errors were encountered:
@ylatuya Just an FYI, I already package fluster for debian from a git tag: https://tracker.debian.org/pkg/fluster
Sorry, something went wrong.
Hello @ylatuya , we have already an automated process to create a release version from the CI, you can see these PRs:
#210 #213 #230
or the next file (release.yml):
https://github.com/fluendo/fluster/blob/master/.github/workflows/release.yml
The release notes after CI (release) workflow, look like this:
No branches or pull requests
Fluster hasn't had a release yet, which we will need to start doing to package it for pypi and Debian.
The proposal is the use to use Conventional Commit Messages in combination with the following github action https://github.com/google-github-actions/release-please-action to automate all the release process.
The text was updated successfully, but these errors were encountered: