## If applied, this commit will... If applied this change will allow goreleaser to handle relative remotes when attempting to parse a repo URL from git. ## Why is this change being made? To fix the error that I recently came across while trying to test my goreleaser configuration: ``` % goreleaser check • checking path= ⨯ configuration is invalid error=invalid scm url: . ⨯ .goreleaser.yml error=configuration is invalid: invalid scm url: . ⨯ command failed error=1 out of 1 configuration file(s) have issues ``` This change happened while on a branch doing some development. As part of that development I needed to test a change to my goreleaser config. My git config at the time looked like (repo obfuscated): ``` % cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = git@gitlab.com:some/repo fetch = +refs/heads/*:refs/remotes/origin/* [branch "main"] remote = origin merge = refs/heads/main [branch "release_fixes"] remote = . merge = refs/heads/main ``` It is fairly common for git to add remotes with a `.` when branch tracking is enabled. While, in general, there aren't many use cases that require a user to need to release from a non-primary branch, there are cases where the user may want to test their configuration with `goreleaser check` and the error of `invalid scm url: .` isn't very helpful. --------- Co-authored-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>
GoReleaser
Deliver Go binaries as fast and easily as possible.
GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.
Get GoReleaser
Documentation
Documentation is hosted live at https://goreleaser.com
Community
You have questions, need support and or just want to talk about GoReleaser?
Here are ways to get in touch with the GoReleaser community:
You can find the links above and all others here.
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.
Badges
GitHub Sponsors
High-tier sponsors of @caarlos0 on GitHub:
OpenCollective
Sponsors
Does your company use goreleaser? Help keep the project bug-free and feature rich by sponsoring the project.
Backers
Love our work and community? Become a backer.
Contributors
This project exists thanks to all the people who contribute. [Contribute].