History

Cadey Ratio e3a389dde4 make dep prune things		2017-12-11 10:38:19 -08:00
..
mg	change from vendor to dep	2017-10-06 08:29:20 -07:00
.gitattributes	change from vendor to dep	2017-10-06 08:29:20 -07:00
.gitignore	change from vendor to dep	2017-10-06 08:29:20 -07:00
.travis.yml	change from vendor to dep	2017-10-06 08:29:20 -07:00
CONTRIBUTING.md	change from vendor to dep	2017-10-06 08:29:20 -07:00
Gopkg.lock	change from vendor to dep	2017-10-06 08:29:20 -07:00
Gopkg.toml	change from vendor to dep	2017-10-06 08:29:20 -07:00
LICENSE	change from vendor to dep	2017-10-06 08:29:20 -07:00
README.md	change from vendor to dep	2017-10-06 08:29:20 -07:00
contrib_test.go	change from vendor to dep	2017-10-06 08:29:20 -07:00
magefile.go	change from vendor to dep	2017-10-06 08:29:20 -07:00
main.go	change from vendor to dep	2017-10-06 08:29:20 -07:00

README.md

mage

Mage is a make/rake-like build tool using Go.

Demo

Discussion

Join the #mage channel on gophers slack for discussion of usage, development, etc.

Documentation

see magefile.org for full docs

see godoc.org/github.com/magefile/mage/mage for how to use mage as a library.

Why?

Makefiles are hard to read and hard to write. Mostly because makefiles are essentially fancy bash scripts with significant white space and additional make-related syntax.

Mage lets you have multiple magefiles, name your magefiles whatever you want, and they're easy to customize for multiple operating systems. Mage has no dependencies (aside from go) and runs just fine on all major operating systems, whereas make generally uses bash which is not well supported on Windows. Go is superior to bash for any non-trivial task involving branching, looping, anything that's not just straight line execution of commands. And if your project is written in Go, why introduce another language as idiosyncratic as bash? Why not use the language your contributors are already comfortable with?

TODO

File conversion tasks