mage
mage copied to clipboard
magefile
a Make/rake-like dev tool using Go
In attempting to setup one git project that has a magefile & sub-packages imported with the `// mage:import` tag and then running mage (with the `-d /path/to/central/mage/project/` and the `-w...
Refers to question/issue #351 It should all work nicely, although it adds that x/sys dependency to detect GOARM at runtime if it's not set, since it's not part of the...
To reproduce this bug, it was necessary to run `go run mage.go test4` several times, because this error is floating ``` // +build mage package main import ( "fmt" "github.com/magefile/mage/mg"...
If I explicitly specify a target on the command line which is also a dependency of _another_ target I specify on the command line, it should only run that target...
Currently, if you attempt to run `mage` from somewhere other than your project root you get an error: ``` No .go files marked with the mage build tag in this...
I had an issue where I used a library in one project's, I used in other, but I forgot to put it to go.mod. All mage did was print this...
Given the following target (imported into main magefile): ```go // Start creates and starts a new MongoDB container using the specified params. // With the exception of name, all params...
# The problem Following the "Zero Install" instructions at https://magefile.org/zeroinstall/ does not work with Go 1.14 or 1.15 when using `go mod vendor`. The `// +build ignore` build constraint in...
I setup my mage target to build locally and it worked fine. Then I wanted to introduce ldflags to get build info embedded as well. The build target errors out....
sh.BothOutput and sh.BothOutputWith follows existing naming conventions.
