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
{{ message }}
This repository has been archived by the owner on Apr 15, 2023. It is now read-only.
I'm contemplating turning the action into a "composite action", which accepts a couple of inputs (like assets) and then calls gh-cli
Or potentially just deprecate and archive the action, which is easier. The advantage of wrapping the CLI in an action is that it would allow slightly easier configuration, e.g.:
automatically picking the latest tag
automatically zipping any folders
It may be worth it, but also I don’t think I'd want to maintain this action further for extremely minimal savings.
This would be a big change, but I think it makes sense (especially because it would save us from release notes generation bugs and further requests).
The v3 of this action and the underlying generator can be forked as they're released under MIT.
Such change would let us drop most of the current code and replace it with: https://github.com/MylesBorins/node-osc/blob/v6.1.11/.github/workflows/create-release.yml#L26-L41
The native generator can be configured separately from this action as well, so most options except
title
,draft
andprerelease
can be dropped as well.It would close:
Context:
The text was updated successfully, but these errors were encountered: