Fix automationProfile to handle args and env parameters

[Copilot]

• Analyze the issue: automationProfile.args and env are ignored in spawnChildProcess
• Identify the code to fix in /src/util.ts
• Implement fix to properly handle args and env parameters from automationProfile
• Add AutomationProfileSetting interface and parseShellSetting helper function
• Add unit tests for parseShellSetting function
• Keep "shell type" label (per reviewer feedback)
• Update test baselines to include "shell args" output

Original prompt

---

This section details on the original issue you should resolve

<issue_title>automationProfile ignores args Parameter</issue_title>
<issue_description>### Brief Issue Summary

I tried setting up the extension with msys2.

Im using both terminal.integrated.profiles.windows and terminal.integrated.automationProfile.windows with identical values.

When compiling via terminal compilation succeeds, when configuring the extension i get a make.exe: command not found error indicating, that the --login option has been ignored and only the path is used.

---

from my settings.json:

"terminal.integrated.automationProfile.windows": {
    "path": "C:/msys64/usr/bin/bash.exe",
    "args": [
        "--login",
        "-i",
    ],
    "env": {
        "MSYSTEM": "UCRT64",
        "CHERE_INVOKING": "1",
        "MSYS2_PATH_TYPE": "inherit",
    },
},

Debug Log

dryrun.log and targets.log:

make.exe --dry-run --keep-going --print-directory
/usr/bin/bash: line 1: make.exe: command not found

___

Additional Information

No response</issue_description>

<agent_instructions>Please add tests if possible.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@gcampbell-msft @koneu Thanks for the issue, we have known issues and/or improvements needed when it comes to the automationProfile settings in VS Code. I'll mark this accordingly and add it to our backlog.

• Fixes automationProfile ignores args Parameter #716

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[snehara99]

@copilot can you keep the "shell type" label instead of changing it to "shell path"? If you strongly believe this should be changed, please explain why. Also existing tests are failing. Please update the tests to account for the new changes.

[Copilot]

@copilot can you keep the "shell type" label instead of changing it to "shell path"? If you strongly believe this should be changed, please explain why. Also existing tests are failing. Please update ...

Reverted "shell path" back to "shell type" and updated the test baselines (test_real_make_nonWin_baseline.out and test_real_make_windows_baseline.out) to include the new "shell args: none" line. Commit 106f7d6.