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
Currently, a combination of gox and ghr is used for the release process.
I'd propose using https://github.com/goreleaser/goreleaser which not only combines both steps but also offers more options to use the released artifacts (docker, brew, snap to name a few). Furthermore, it would be possible to seamlessly integrate with goreleasers' inverse https://github.com/goreleaser/godownloader. Which automatically generates download bash scripts for a released artifact version based on the .goreleaser.yml.
This would make it easier to use the git-chglog tool for artifacts and in pipelines.
gh-actions
Furthermore, use github actions for ci as travis does not respond back to the PRs. See comment
The text was updated successfully, but these errors were encountered:
Proposal
for new release process of the artifacts and homebrew taps at https://github.com/git-chglog/homebrew-git-chglog
Goreleaser
Currently, a combination of
gox
andghr
is used for the release process.I'd propose using https://github.com/goreleaser/goreleaser which not only combines both steps but also offers more options to use the released artifacts (docker, brew, snap to name a few). Furthermore, it would be possible to seamlessly integrate with
goreleasers'
inverse https://github.com/goreleaser/godownloader. Which automatically generates download bash scripts for a released artifact version based on the.goreleaser.yml
.This would make it easier to use the
git-chglog
tool for artifacts and in pipelines.gh-actions
Furthermore, use github actions for ci as travis does not respond back to the PRs. See comment
The text was updated successfully, but these errors were encountered: