Scripts in automation and working directories

Currently it seems like all scripts/jobs running in Automation uses the Repository Path as their working directory, which may cause various files to be created if you’re not explicit in your scripts about where to put said files. I presume this could cause a lot of junk with Git Sync.

Could we maybe get an option to specify a working directory for our scripts (potentially with parameters like the jobid), and/or have the default moved to another directory so it isn’t the Repository Path?

Product: PowerShell Universal
Version: 3.0.3
1 Like

I’ve opened an issue for that here: Working directory for scripts · Issue #1267 · ironmansoftware/issues · GitHub

1 Like