Documentation for MAGEFILE_CACHE is not consistent with actual behavior on Windows

[WilliamRoyNelson]

https://github.com/magefile/mage/blob/master/site/content/environment/_index.en.md?plain=1#L14-L17

## MAGEFILE_CACHE

Sets the directory where mage will store binaries compiled from magefiles
(default is $HOME/.magefile)

mage/site/content/howitworks/_index.en.md

Lines 15 to 18 in 9f54e0f

	## Binary Cache
	Compiled magefile binaries are stored in $HOME/.magefile. This location can be
	customized by setting the MAGEFILE_CACHE environment variable.

## Binary Cache

Compiled magefile binaries are stored in $HOME/.magefile.  This location can be
customized by setting the MAGEFILE_CACHE environment variable.

mage/mg/runtime.go

Lines 110 to 114 in 9f54e0f

	switch runtime.GOOS {
	case "windows":
	return filepath.Join(os.Getenv("HOMEDRIVE"), os.Getenv("HOMEPATH"), "magefile")
	default:
	return filepath.Join(os.Getenv("HOME"), ".magefile")

	switch runtime.GOOS {
	case "windows":
		return filepath.Join(os.Getenv("HOMEDRIVE"), os.Getenv("HOMEPATH"), "magefile")
	default:
		return filepath.Join(os.Getenv("HOME"), ".magefile")

On Windows, instead of creating a folder at %USERPROFILE%\.magefile as would be expected by the documentation, a folder is created at %USERPROFILE%\magefile

[WilliamRoyNelson]

Docs fix PR: #484

[mloskot]

This can be closed since

• Update documentation to include Windows Magefile Cache #484

has been merged by @natefinch

@WilliamRoyNelson It is a good idea to use the GitHub features of Closing Issues via Commit Messages next time, so related issues are not left dangling after merge.

[WilliamRoyNelson]

This can be closed since

• Update documentation to include Windows Magefile Cache #484

has been merged by @natefinch

@WilliamRoyNelson It is a good idea to use the GitHub features of Closing Issues via Commit Messages next time, so related issues are not left dangling after merge.

That is an awesome feature that I was not aware of. I will make sure to do that in the future!