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.
I have a goreleaser setup that pushes docker images and manifest lists on tag builds AND on builds of certain branches (e.g. our main branch). To do this successfully for branches, I need to disable the changelog and release configurations. But I still want to publish docker images and docker manifests.
Describe the solution you'd like
I see that as of #3710, I can now template release.disable to use something like {{ eq .Tag ""} or {{ .Env.DISABLE }}.
I'd like to make changelog.skip template-able in the exact same way that release.disable is so that I can use the same template to enable/disable them together.
Describe alternatives you've considered
Right now my workaround is to set release.disable and changelog.skip to true in my goreleaser config. But then during CI, I modify the goreleaser config file just before the goreleaser release call to set release.disable and changelog.skip to false when its a tag build.
Search
I did search for other open and closed issues before opening this.
Code of Conduct
I agree to follow this project's Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have a goreleaser setup that pushes docker images and manifest lists on tag builds AND on builds of certain branches (e.g. our
main
branch). To do this successfully for branches, I need to disable the changelog and release configurations. But I still want to publish docker images and docker manifests.Describe the solution you'd like
I see that as of #3710, I can now template
release.disable
to use something like{{ eq .Tag ""}
or{{ .Env.DISABLE }}
.I'd like to make
changelog.skip
template-able in the exact same way thatrelease.disable
is so that I can use the same template to enable/disable them together.Describe alternatives you've considered
Right now my workaround is to set
release.disable
andchangelog.skip
to true in my goreleaser config. But then during CI, I modify the goreleaser config file just before thegoreleaser release
call to setrelease.disable
andchangelog.skip
to false when its a tag build.Search
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: