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
After browsing and exploring a bit the project, I'd like to bring some ideas to enhance the project.
My first thought is that the project lacks some documentation, like a docs website or anything similar.
Moreover, it isn't really compatible w/ other tools or actions, such that you can configure the tool as you wish and manage each step of the release process, compared to the original semantic-release.
But the tool is far easier to use, as it's only a binary. (and in general, when you escape the NodeJS ecosystem... 😆)
One example scenario is using this tool for managing versions automatically and use another action for managing the release process.
Thus, I can run the go-semantic-release/action until it founds a new version to release, then use the goreleaser/action for managing the release process based on the new version tag pushed by the first action.
As a result, it allows for a more configurable way of releasing software, while not having issues w/ plugin versioning, hooks, ...
I can take some time to help contribute the project for docs or other ideas if you'd like.
Also, I completely understand that managing such open-source project can be time-consuming.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
After browsing and exploring a bit the project, I'd like to bring some ideas to enhance the project.
My first thought is that the project lacks some documentation, like a docs website or anything similar.
Moreover, it isn't really compatible w/ other tools or actions, such that you can configure the tool as you wish and manage each step of the release process, compared to the original
semantic-release
.But the tool is far easier to use, as it's only a binary. (and in general, when you escape the NodeJS ecosystem... 😆)
One example scenario is using this tool for managing versions automatically and use another action for managing the release process.
Thus, I can run the
go-semantic-release/action
until it founds a new version to release, then use thegoreleaser/action
for managing the release process based on the new version tag pushed by the first action.As a result, it allows for a more configurable way of releasing software, while not having issues w/ plugin versioning, hooks, ...
I can take some time to help contribute the project for docs or other ideas if you'd like.
Also, I completely understand that managing such open-source project can be time-consuming.
Wish you the best !
Beta Was this translation helpful? Give feedback.
All reactions