Magefile.org Website Review

Mage has no dependencies outside the Go standard library, and builds with Go 1.7 and above (possibly even lower versions, but they’re not This will do*nload the code into your GOPATH, and then run the bootstrap script to build mage with version infomation embedded in it. A normal go get (without -d) will build the binary correctly, but no version info will be embedded. If you’ve done this, no worries, just     if err := sh.Run(dep, ensure); err != nil {         return err Run the above Build target by simply running mage build in the same directory as the magefile. There are no plugins. You don’t need plugins. It’s just Go code. You can import whatever libraries you want. Every library in the go ecosystem is a mage plugin. Every tool you use with Go can be used with Magefiles.             output a static binary to the given path   -init     create a starting template if no mage files exist   -l        list mage targets in this directory   -h        show this help             run magefiles in the given directory (default .)   -debug    turn on debug messages   -h        show description of a target   -f        force recreation of compiled magefile   -keep     keep intermediate mage files around after running   -gocmd              use the given go binary to compile the output (default: go)   -goos     sets the GOOS for the binary created by -compile (default: current OS)   -goarch   sets the GOARCH for the binary created by -compile (default: current arch)   -t              timeout in duration parsable format (e.g. 5m30s)   -v        show verbose output when running mage targets Makefiles are hard to read and hard to write. Mostly because makefiles are essentially fancy bash scripts with significant white space and