BC Observatoryunofficial, made by waldo
code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#2331 Support trackALAlertsInGitHub for workspace compilation build path

AL-Go now produces error log files during workspace compilation when GitHub code scanning alerts are enabled, allowing AL compiler diagnostics to surface as code scanning alerts in the workspace build path.

Open in Claude2331.mdPull request #2331

Pull request · merged into main on 2026-08-13 by aholstrup1 · 4 files (+182 -1), 2 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • Error log directory argument passed to altool workspace compile when trackALAlertsInGitHub is enabled
  • Each project generates errorLog.json diagnostics file into .buildartifacts/ErrorLogs/ folder
  • Gracefully skips –errorlogdirectory if compiler does not support it with a warning
  • Matches existing behavior from classic Run-AlPipeline build path
  • Tests and release notes added
  • Behaviour changes for users or extensions.

AL objects touched

  • Actions/.Modules/CompileFromWorkspace.psm1: modified, not in the BC? snapshot
  • Actions/CompileApps/Compile.ps1: modified, not in the BC? snapshot

Context

  • Systems: development, platform
  • From the description: “AL-Go passes --errorlogdirectory to altool workspace compile so each project emits an *.errorLog.json diagnostics file”

Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).