env icon indicating copy to clipboard operation
env copied to clipboard

If a build fails for any reason, the generated env.txt stays there, and then causes an exception for the next build

Open semateos opened this issue 1 year ago • 0 comments

Rather than throw an exception when it discovers an existing env.txt file, maybe just remove it? Or maybe just throw a warning rather than a build halting exception. Or maybe there's an OnBuildFailed event where it could clean that up. It's a nuisance to have to manually delete the file that was auto generated.

Thanks for the nifty little utility! Much appreciated.

semateos avatar Mar 05 '24 22:03 semateos