We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
folder
directory
# .goreleaser.yaml aurs: - name: foo-bin directory: foo-bin
Results in:
$ tree -a . . ├── foo-bin │ ├── .SRCINFO │ └── PKGBUILD
# .goreleaser.yaml brews: - name: foo # Folder inside the repository to put the formula. folder: Formula
$ tree -a . . ├── Formula │ ├── foo.rb
Would be nice (for consistency) to settle either on directory or folder.
$ goreleaser --version ____ ____ _ / ___| ___ | _ \ ___| | ___ __ _ ___ ___ _ __ | | _ / _ \| |_) / _ \ |/ _ \/ _` / __|/ _ \ '__| | |_| | (_) | _ < __/ | __/ (_| \__ \ __/ | \____|\___/|_| \_\___|_|\___|\__,_|___/\___|_| goreleaser: Deliver Go Binaries as fast and easily as possible https://goreleaser.com GitVersion: v1.24.1-0.20240308165802-85f213c9da5e GitCommit: unknown GitTreeState: unknown BuildDate: unknown BuiltBy: unknown GoVersion: go1.22.1 Compiler: gc ModuleSum: h1:DvK8/lL/M513VkviSCuNSZXImqyP7Df+AjpdyTqbejU= Platform: darwin/arm64
No response
The text was updated successfully, but these errors were encountered:
you're right, just opened #4737 fixing this!
thanks for the thoughtful issue 🙏
Sorry, something went wrong.
feat: consistently use directory in property names (#4737)
7fc9399
It was a mess of "folder" x "directory", so changed it all to "directory". Closes #4732
caarlos0
Successfully merging a pull request may close this issue.
Description
For AUR (docs):
Results in:
For Homebrew (docs):
Results in:
Proposal
Would be nice (for consistency) to settle either on
directory
orfolder
.goreleaser version
output
GoReleaser Check
Search
Supporter
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: