[business-central-bot]

preview

Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available.

Copilot code review for AL pull requests

AL-Go repositories can now opt in to AI-powered review of AL pull requests, with configurable models, target branches, excluded authors, and BCQuality skills and knowledge. See Enable Copilot code review for setup, organization policy requirements, and operational details.

Issues

• Issue 2398 - Preserve dependency paths containing commas when passing a single app to Run-AlPipeline. Download Project Dependencies now warns with the complete path if a resolved dependency file is missing, without changing the output lists.

• Issue 2390 - AnalyzeTests no longer crashes under strict mode when a page scripting test suite contains both passed and failed tests, preserving the failure summary.

• Issue 2387 - Deployment environment discovery now paginates GitHub API results, so Publish To Environment and CI/CD can discover environments beyond the first 30 and read their branch policies.

Related to AB#640900

BCApps reviewer policy carried forward

This uptake migrates BCApps from the reusable microsoft/BC-ALAgents reviewer to native AL-Go. The policy must be explicit in .github/AL-Go-Settings.json; copying the raw preview workflows alone leaves automatic reviews disabled.

• CodeReviewAgent.enabled: true; target branch main, matching the existing intake rather than widening review scope to all PR-build branches.
• Exclude business-central-bot[bot], preserving the existing automation-author exclusion. Native review context also skips draft PRs.
• Root model gpt-5.6-sol and leaf model gpt-5.6-luna, matching the previous reusable workflow defaults.
• Trusted marketplace https://github.com/microsoft/BCQuality, content version 1.7 supplied by this AL-Go preview (a deliberate update from the old reusable engine's pinned 1.6 content).
• Retain only the microsoft layer and microsoft/knowledge/**; no disabled skills or denied articles, preserving the existing Microsoft-only content policy rather than inheriting AL-Go's all-layer default.
• Existing BCApps build settings, project layout, artifact selection, analyzers, runner configuration, environment protections, and CI branch patterns are unchanged. The native reviewer retains AL/W1/all-application-area task context; unsupported legacy input names were not added to settings.

Generated workflow activation

The official updater attempt 39835004965 was rejected before the update job ran because the PR branch is not allowed to deploy to Official-Build. No environment protection, approval, secret, or repository policy was changed.

The two enabled review triggers were instead generated locally using the exact published AL-Go YAML class and trigger-generation code at 959519dfe53da49b83bd5cf1f43eaa0be7ca5301, then committed normally to this PR. This is a secret-free code-generation operation, not a deployment. The generated workflows are the published templates plus only the three-line pull_request and three-line workflow_run trigger additions; future AL-Go updates retain them through the checked-in settings.

The native adapter retains the previous reviewer behavior defaults: Medium minimum severity, 25 findings per domain, serial leaves, 30-minute CLI timeout, parse errors surfaced, and no overview summary comment. These are engine defaults, not unsupported repository settings.

Additional scope on top of the original updater PR: three files, 31 added lines (25 settings lines and six generated trigger lines). Settings were validated against the exact pinned schema, all other BCApps settings were compared unchanged, and both generated workflows were checked against the published templates plus their enabled triggers. The preview template revision is unchanged. This PR has not been merged.

[Alexander Holstrup (aholstrup1)]

We need to wait with this PR until we have uptaken the new settings so we don't accidently disable the code reviewer