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
I understand, that some project don't have a .goreleaser.yml file included in their repository, but I have, since I wanna build a project for Windows and some other platforms.
Currently the goreleaser.yml is overwritten by Rabbit and there seems no way of preventing Rabbit to do so.
Can we implement a check if there is an .goreleaser.yml and skip creation of the default .goreleaser.yml? How do we handle different archive types (zip vs tar.gz) then? How to pass the project name, when it's not included in the YAML?
The text was updated successfully, but these errors were encountered:
because it was the easiest way otherwise rabbit has to figure out automatically what have been released. I totally agree that we shouldn't override the .goreleaser.yml if it exists and then move anything that got created to release directory.
I understand, that some project don't have a
.goreleaser.yml
file included in their repository, but I have, since I wanna build a project for Windows and some other platforms.Currently the
goreleaser.yml
is overwritten by Rabbit and there seems no way of preventing Rabbit to do so.Can we implement a check if there is an
.goreleaser.yml
and skip creation of the default.goreleaser.yml
? How do we handle different archive types (zip vs tar.gz) then? How to pass the project name, when it's not included in the YAML?The text was updated successfully, but these errors were encountered: