Trigger full PR build on changes under src/Layers

[aholstrup1]

What & why

Incremental PR builds (incrementalBuilds.onPull_Request: true) only build projects whose appFolders/testFolders cover the modified files. The src/Layers/* folders (for example src/Layers/NL/BaseApp, src/Layers/W1/BaseApp) are consumed by projects but are not listed as project folders, so a PR that only touches a layer maps to zero projects. The "Determine Projects To Build" step then logs Did not find any projects to add to the build order, emits ProjectsJson=[], and every build job is skipped, producing a green PR build that compiled nothing.

Rather than disable incremental builds entirely, this adds a fullBuildPatterns entry for src/Layers/*. AL-Go's DetermineProjectsToBuild matches modified files against these patterns with PowerShell -like (where * spans path separators), so any change nested under src/Layers forces a full Pull Request build. Normal app-only changes keep fast incremental builds.

Linked work

AB#640966

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome

Configuration-only change to .github/AL-Go-Settings.json; no app code affected, so no AL build or BC run applies. Root cause verified against the failing run on PR #8933 (run 28448705321), where the Initialization job logged Did not find any projects to add to the build order and ProjectsJson=[], causing all Build jobs to be skipped. Pattern semantics confirmed from AL-Go DetermineProjectsToBuild.psm1 (IsFullBuildRequired uses $modifiedFiles -like $fullBuildFolder after joining with the base folder).

Risk & compatibility

Low. Incremental builds stay enabled, so the only behavior change is that PRs touching src/Layers/* now build all projects (intended). If additional shared-but-unmapped roots are found later, they can be added to fullBuildPatterns the same way.

[github-actions]

Copilot PR Review

Iteration 2 · Outcome: not-applicable

The diff contains no AL source changes (only .github/AL-Go-Settings.json, a CI/build-pipeline configuration file). All six AL-domain sub-skills declined with outcome 'not-applicable' because the task context lacks an AL dimension.

Knowledge source: https://github.com/microsoft/BCQuality@822cae1b2771ac25f665f73369f69093bd4fd630

No findings were posted for this iteration.

Orchestrator pre-filter (13 file(s) excluded)

• layer-disabled (knowledge) : 13 file(s)

_{Findings produced by the Copilot CLI agent against BCQuality at 822cae1b2771ac25f665f73369f69093bd4fd630. Reply 👎 on any inline comment to flag false positives.}