You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current release flow for Fluentd creates a tag in the format vX.Y.Z which works fine for direct use by Ruby but doesn't follow the GitHub idiom of creating a "GitHub Release". As the GitHub idiom isn't being followed the latest version isn't shown on the repo default view, you can't watch releases and getting the latest version via the API is more complicated than it could be.
Describe the solution you'd like
I'd like a GitHub Actions workflow to be added that watches for the release tags to be pushed to the repo. This workflow can make the tag into a "GitHub Release" with all of the benefits that entails.
This workflow could also be used to automate the creation of an issue and potentially a PR in the fluent/fluentd-docker-image repo.
Describe alternatives you've considered
n/a
Additional context
I'll open a PR to do this and for the implementation to be discussed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current release flow for Fluentd creates a tag in the format
vX.Y.Z
which works fine for direct use by Ruby but doesn't follow the GitHub idiom of creating a "GitHub Release". As the GitHub idiom isn't being followed the latest version isn't shown on the repo default view, you can't watch releases and getting the latest version via the API is more complicated than it could be.Describe the solution you'd like
I'd like a GitHub Actions workflow to be added that watches for the release tags to be pushed to the repo. This workflow can make the tag into a "GitHub Release" with all of the benefits that entails.
This workflow could also be used to automate the creation of an issue and potentially a PR in the fluent/fluentd-docker-image repo.
Describe alternatives you've considered
n/a
Additional context
I'll open a PR to do this and for the implementation to be discussed.
The text was updated successfully, but these errors were encountered: