bingo
bingo copied to clipboard
Like `go get` but for Go tools! CI Automating versioning of Go binaries in a nested, isolated Go modules.
**`bingo version` output**: v0.5.2 **`go version` output**: go version go1.18 darwin/arm64 **What happened**: I'm running with `bingo get github.com/plexsystems/[email protected]` which looks like: ``` module _ // Auto generated by https://github.com/bwplotka/bingo....
Technically it's as easy as replace: ``` module _ // Auto generated by https://github.com/bwplotka/bingo. DO NOT EDIT go 1.17 replace github.com/githubnemo/CompileDaemon => github.com/ypresto/CompileDaemon v1.3.1-0.20220406082449-39bc1352dc62 require github.com/githubnemo/CompileDaemon v1.4.0 ``` This works,...
Currently, we install real modules, let's craft something lightweight in git for test purposes instead. This will make test much faster and will not require things like https://github.com/bwplotka/bingo/issues/28
**`bingo version` output**: ```sh ❯ bingo version v0.5.1 ``` **`go version` output**: ```sh ❯ go version go version go1.15.9 linux/amd64 ``` **What happened**: listing of installed module/package failed **What you...
Sourcing `.bingo/variables.env` and running `$TOOL_NAME` work great on the terminal, but it's less intuitive than simply calling `tool-name`, as it would be if the tool were installed with `go install`....
**`bingo version` output**: ```sh ❯ bingo version v0.5.1 ``` **`go version` output**: ```sh ❯ go version go version go1.15.9 linux/amd64 ``` **What happened**: installation of a module (shfmt) failed but...
**`bingo version` output**: ```sh ❯ bingo version v0.5.1 ``` **`go version` output**: ```sh ❯ go version go version go1.15.9 linux/amd64 ``` **What happened**: installation of a module created a broken...
Thanks @kakkoyun for sharing this: https://go-review.googlesource.com/c/proposal/+/243077/2/design/30515-go-get-b.md
**`go version` output**: ```sh ❯ go version go version go1.15.9 linux/amd64 ``` **What happened**: installation failed **What you expected to happen**: installation succeed **How to reproduce it (as minimally and...
I always need it and always do that manually ): Let's automate!