Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use own .goreleaser.yml from repository? #46

Open
fabiang opened this issue Jun 20, 2019 · 1 comment
Open

How to use own .goreleaser.yml from repository? #46

fabiang opened this issue Jun 20, 2019 · 1 comment
Labels
enhancement New feature or request Hacktoberfest

Comments

@fabiang
Copy link

fabiang commented Jun 20, 2019

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?

@Clivern
Copy link
Owner

Clivern commented Jun 21, 2019

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.

@Clivern Clivern added the enhancement New feature or request label Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Hacktoberfest
Projects
None yet
Development

No branches or pull requests

2 participants