Support trackALAlertsInGitHub for workspace compilation build path

[aholstrup1]

❔What, Why & How

trackALAlertsInGitHub surfaces AL compiler diagnostics as GitHub code scanning alerts, but it only worked on the classic Run-AlPipeline build path. When workspaceCompilation (preview) was enabled, no *.errorLog.json files were produced, so no alerts appeared even with the setting turned on.

This wires the same behavior into the workspace compilation path. When both trackALAlertsInGitHub and workspaceCompilation are enabled, AL-Go passes --errorlogdirectory to altool workspace compile so each project emits an *.errorLog.json diagnostics file into its .buildartifacts/ErrorLogs/ folder. From there the existing upload + ProcessALCodeAnalysisLogs pipeline picks them up, converts them to SARIF, and publishes code scanning alerts, matching the classic build behavior.

The --errorlogdirectory argument is threaded through via a GenerateErrorLog switch driven by $settings.trackALAlertsInGitHub. If the consumed compiler version does not yet support --errorlogdirectory, the option is skipped and a warning is logged so the rest of the build is unaffected (no silent no-op, no hard failure).

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry

[Copilot]

Pull request overview

Extends GitHub AL alert tracking to workspace compilation.

Changes:

• Adds compiler capability detection and --errorlogdirectory forwarding.
• Connects alert settings to workspace builds.
• Adds Pester coverage and release notes.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
Actions/.Modules/CompileFromWorkspace.psm1	Adds error-log support and capability probing.
Actions/CompileApps/Compile.ps1	Configures the diagnostics output directory.
Tests/CompileFromWorkspace.Test.ps1	Tests error-log argument construction.
RELEASENOTES.md	Announces workspace compilation alert support.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

Actions/.Modules/CompileFromWorkspace.psm1:476

• A failed native executable does not throw solely because it exits nonzero, so this catch does not reliably detect a failed help probe. If the failed invocation emits usage text containing the option, this returns true and the subsequent compile can hard-fail instead of taking the promised warning/fallback path. Check $LASTEXITCODE before matching the output (or invoke through RunAndCheck, which already enforces this).

        $compileHelp = & $ALToolPath workspace compile --help 2>&1 | Out-String
        return ($compileHelp -match [regex]::Escape($Option))

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

Actions/.Modules/CompileFromWorkspace.psm1:476

• The compatibility probe runs a native executable but never checks $LASTEXITCODE. On Windows PowerShell 5 and default PowerShell 7 behavior, a non-zero native exit is not guaranteed to enter catch, so failed help probes can still be parsed as successful output instead of taking the intended unsupported-compiler fallback. Capture and check the exit code immediately after invocation and return $false for any non-zero result.

        $compileHelp = & $ALToolPath workspace compile --help 2>&1 | Out-String
        return ($compileHelp -match [regex]::Escape($Option))

Actions/.Modules/CompileFromWorkspace.psm1:466

• This new function has no direct Pester coverage: all three added tests mock it, so the actual help-output matching and failed-probe fallback are never exercised. Add InModuleScope tests for supported output, unsupported output, and a failed/non-zero invocation.

function Test-ALToolWorkspaceCompileSupportsOption {

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

Actions/.Modules/CompileFromWorkspace.psm1:366

• The added tests invoke CompileAppsInWorkspace with ErrorLogDirectory directly, so they do not verify this new Build-AppsInWorkspace forwarding path or the trackALAlertsInGitHub setting that supplies it. The existing workspace-compilation E2E scenario also neither enables the setting nor asserts an ErrorLogs artifact, despite the PR checklist claiming E2E coverage. Please add a forwarding unit test and update the E2E scenario to exercise the user-facing path.

        ErrorLogDirectory = $ErrorLogDirectory