Nate Finch

add version info automatically if you build with go 1.18+

1

The only reason we have an install script is to set build data. As of 1.18, we don't need that anymore. So, now the logic will be split, if you...

**Describe the feature** The only reason we have a build script for mage is to embed version information in the binary. As of 1.18, go will do that automatically. We...

VSCode support for running mage tasks

5

Could be as easy as running tests, where a clickable link is inserted above each task.

The generated mage_output_file.go uses imports like "log" which can easily conflict with global variables in a user's magefile, so we should name them something unlikely to collide with people's own...

document best practices

1

Examples of dependencies, usage of sh and mg, how to structure files for readability, etc.

Mage fails if you run it in module mode w/o go.mod

4

If you run mage in a package outside gopath (i.e. using modules), when it tries to run `go list` to determine the files it needs to build, `go list` will...

Just as we auto-expand env vars, it would be nice to expand glob (*.foo) into the correct filenames. Also possibly add a config variable `var AutoGlob=false`

I'm using mage in a monorepo project with a small set of core targets (e.g., `test`, `build`, `package`, `deploy`, etc.) that are consistent across all "sub-projects" in the monorepo. Each...

if you run `mage -d ./foo` when using modules and your *current* directory isn't a modules project, it'll fail, saying it doesn't know where to find the project. The fix...

Warn if additional args when running mage commands like --version etc

1

bail if either flag is set if fs.NArgs() > 0 || fs.NFlags() > 1 - i.e. if any other args were specified. Also move them into a separate section of...