Enhance customALGoFiles feature by OleWunschmann · Pull Request #2273 · microsoft/AL-Go

OleWunschmann · 2026-06-03T15:24:31Z

❔What, Why & How

This pull request enhances the AL-Go template update system by introducing a new mechanism for unconditionally removing files from repositories, expanding file specification options, and improving the logic for determining which files to include, exclude, or remove during updates. The changes also improve documentation and schema validation, and add new helper functions to streamline file resolution.

Key changes:

1. File Removal Functionality

Added support for a new filesToRemove array in settings, allowing unconditional removal of files from repositories during updates, regardless of whether they exist in the template. This is reflected in both the PowerShell logic and the settings schema. [1] [2] [3] [4]

2. File Specification Enhancements

Introduced the destinationName property to file specifications, enabling files to be renamed when copied or removed, and updated the schema and logic accordingly. [1] [2]
Improved descriptions and documentation for filesToInclude and filesToExclude in the schema, clarifying propagation and behavior. [1] [2]

3. Update Logic Improvements

Refactored the logic for determining files to include, exclude, and remove:
- Now merges default, repository, and (if present) original template settings for all three categories.
- Deduplicates files based on destination paths.
- Ensures files in filesToRemove are excluded from inclusion, and that exclusions are mapped more accurately. [1] [2]

4. Helper Functions and Documentation

Added ResolveFilePathsInDestinationFolder, a helper for resolving file specs that refer to files already in the destination (e.g., for removal), with detailed documentation.
Improved and clarified documentation for key functions, especially around file resolution and settings snapshot updates.

5. Minor Path Handling Fixes

Ensured that sourceFolder always has a trailing slash in file path resolution to prevent path errors.

Related to discussion: #2227

✅ Checklist

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

Copilot

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR enhances the customALGoFiles behavior during “Update AL-Go System Files”, adding support for unconditional removals (filesToRemove) and improving custom-template behavior by merging template settings directly and resolving files from the original AL-Go template where applicable.

Changes:

Add customALGoFiles.filesToRemove support end-to-end (schema, defaults, resolution logic, docs, and release notes).
Update CheckForUpdates to read template repo settings via ReadSettings and merge template settings during file resolution.
Expand automated coverage (unit + e2e) for include/exclude/remove resolution and custom-template propagation.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
e2eTests/scenarios/CustomTemplate/runtest.ps1	Extends e2e scenario to validate custom-template file include/exclude/remove propagation and workflow presence.
Tests/CheckForUpdates.Action.Test.ps1	Adds unit tests for destination-folder resolution and expanded `GetFilesToUpdate` behaviors (including `filesToRemove`).
Actions/CheckForUpdates/CheckForUpdates.ps1	Updates settings reading (incl. `trigger`) and wires template settings + `filesToRemove` into update/removal flow.
Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1	Implements `ResolveFilePathsInDestinationFolder` and extends `GetFilesToUpdate` to produce include/exclude/remove lists.
Actions/.Modules/settings.schema.json	Extends settings schema with `customALGoFiles.filesToRemove` and clarifying descriptions.
Actions/.Modules/ReadSettings.psm1	Adds default `filesToRemove` array under `customALGoFiles`.
Scenarios/settings.md	Documents `customALGoFiles.filesToRemove` in settings reference.
Scenarios/CustomizingALGoForGitHub.md	Adds conceptual docs + examples for original-template resolution and `filesToRemove`.
RELEASENOTES.md	Documents enhanced `customALGoFiles` behavior and new `filesToRemove`.

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

OleWunschmann · 2026-06-09T16:28:58Z

+                            "sourceFolder": {
+                                "type": "string",
+                                "description": "The source folder from which to remove files, relative to the template repository root."
+                            },
+                            "filter": {
+                                "type": "string",
+                                "description": "A filter string to select which files to remove. It can contain '*' and '?' wildcards."
+                            },
+                            "destinationFolder": {
+                                "type": "string",
+                                "description": "The destination folder where the files should be removed, relative to the repository root."
+                            },
+                            "perProject": {
+                                "type": "boolean",
+                                "description": "Indicates whether the removal should be applied per project. In that case, destinationFolder is relative to each project folder."
+                            }
+                        }


I added the support for destinationName based on the same property of filesToInclude, which is also not documented or defined in the schema.

@mazhelez What do you think about adding the property for filesToInclude and filesToRemove in the documentation and schema?

I extended the schema and documentation for property destinationName

OleWunschmann · 2026-06-09T16:31:13Z

@mazhelez The failing PS5 tests should be fixed now.

…es-feature

mazhelez · 2026-07-15T21:31:28Z

                    }
+                },
+                "filesToRemove": {
+                    "description": "An array of file specifications to unconditionally remove from the repository during 'Update AL-Go System Files', regardless of whether the files exist in the template. Useful for cleaning up files that have been removed from the template but may still exist in repositories.",


... regardless of whether the files exist in the template

That's the part that made us leave out filesToRemove from the initial implementation of "custom AL-Go files".

If the files are not in the template, they are not considered AL-Go files, so why would AL-Go clean them up?

Right now a custom template (and AL-Go) cannot remove/rename a file, because these changes in the template are not propagated to repos that use it.
The current workaround is to keep the file in the template and add it to "filesToExclude". This works, but it’s messy and pollutes the template repository.

With filesToRemove a custom template could remove files in the final repositories without the need to keep them.

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1205

Removal destinations are not constrained to $baseFolder. A filesToRemove entry with a matching template file and destinationFolder = '..' produces a destinationFullPath outside the repository; CheckForUpdates.ps1 later converts it to a relative path and passes it to Remove-Item. Normalize every removal destination and reject paths that are not descendants of the repository root before returning this list.

        $filesToRemove += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    }
    $filesToRemove += @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

+    if ($null -ne $templateSettings) {
+        $filesToIncludeUnresolved += $templateSettings.customALGoFiles.filesToInclude
+    }
+    $filesToIncludeUnresolved += $settings.customALGoFiles.filesToInclude


OleWunschmann · 2026-07-21T18:43:00Z

+$removeFiles = @($filesToExclude) + @($filesToRemove) | Where-Object { $_ -and (Test-Path -Path $_.destinationFullPath -PathType Leaf) } | ForEach-Object {
    $relativePath = Resolve-Path -Path $_.destinationFullPath -Relative


These issues are already in the codebase and worked fine until now.

OleWunschmann · 2026-07-23T19:55:25Z

+| Yes | No | Yes | File from **original template** is propagated |
+| No | Yes | Yes | File from **custom template** is propagated |
+| Yes | Yes | Yes | File from **custom template** is used (takes precedence) |


Copilot

Pull request overview

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

Comments suppressed due to low confidence (1)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1205

The source-path boundary check does not validate the generated destination. A spec can match a legitimate template file while setting destinationFolder to ../..., producing a filesToRemove entry outside $baseFolder; CheckForUpdates.ps1 later converts that to a relative traversal path and passes it to Remove-Item. Normalize each destinationFullPath and reject entries outside the repository root before returning this removal list.

        $filesToRemove += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    }
    $filesToRemove += @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

OleWunschmann · 2026-07-23T19:55:11Z

+    # Determine files to include
+    $filesToIncludeUnresolved = GetDefaultFilesToInclude -includeCustomTemplateFiles:$hasOriginalTemplate
+    if ($null -ne $templateSettings) {
+        $filesToIncludeUnresolved += $templateSettings.customALGoFiles.filesToInclude
+    }
+    $filesToIncludeUnresolved += $settings.customALGoFiles.filesToInclude
+    $filesToInclude = @()
+    if ($hasOriginalTemplate) {
+        $filesToInclude += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToIncludeUnresolved -projects $projects)
+    }
+    $filesToInclude += @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToIncludeUnresolved -projects $projects)
+    # Remove duplicates based on destinationFullPath, keeping the last one (setting > template settings > defaults; template folder > original template folder)
+    $filesToInclude = @($filesToInclude | Group-Object { $_.destinationFullPath } | Sort-Object -Property Name | ForEach-Object { $_.Group[-1] })


The comment was wrong and was fixed. Additionally I optimized the logic some more.

OleWunschmann · 2026-07-23T19:55:16Z

+    # Determine files to exclude
+    $filesToExcludeUnresolved = GetDefaultFilesToExclude -settings $settings
+    if ($null -ne $templateSettings) {
+        $filesToExcludeUnresolved += $templateSettings.customALGoFiles.filesToExclude
+    }
+    $filesToExcludeUnresolved += $settings.customALGoFiles.filesToExclude
+    $filesToExclude = @()
+    if ($hasOriginalTemplate) {
+        $filesToExclude += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToExcludeUnresolved -projects $projects)
+    }
+    $filesToExclude += @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToExcludeUnresolved -projects $projects)
+    # Remove duplicates based on destinationFullPath, keeping the last one (setting > template settings > defaults; template folder > original template folder)
+    $filesToExclude = @($filesToExclude | Group-Object { $_.destinationFullPath } | Sort-Object -Property Name | ForEach-Object { $_.Group[-1] })


The comment was wrong and was fixed. Additionally I optimized the logic some more.

OleWunschmann · 2026-07-23T19:52:52Z

+(Join-Path (Get-Location) $defaultCustomFileName) | Should -Not -Exist
+# Check that optional custom file is NOT present in final repository
+(Join-Path (Get-Location) $optionalCustomFileName) | Should -Not -Exist
+# Check that legacy workflow file is present in final repository


Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

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

Comments suppressed due to low confidence (3)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1178

The stated precedence is not applied within a source folder. ResolveFilePaths suppresses duplicate destinationFullPath values as it iterates, and this unresolved list is ordered defaults → template settings → repository settings, so the first/default or template entry wins before this grouping can keep the last entry. A repository include targeting the same destination as a template include is therefore silently ignored. Resolve all candidates before deduplicating, or process the specifications in precedence order.

    # Remove duplicates based on destinationFullPath, keeping the last one (setting > template settings > defaults; template folder > original template folder)
    $filesToInclude = @($filesToInclude | Group-Object { $_.destinationFullPath } | Sort-Object -Property Name | ForEach-Object { $_.Group[-1] })

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1205

Template-resolved removals can produce a destinationFullPath outside $baseFolder: for example, an entry with destinationFolder = '..' is resolved from a valid template source and retained here, even though destination-folder resolution rejects the escaped target. The caller later converts this path to ../... and passes it to Remove-Item in the cloned workspace, enabling deletion attempts outside the repository or causing the update to fail. Normalize each destination with GetFullPath and reject paths that are not strictly within $baseFolder before returning removal entries.

    $filesToRemove += @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

e2eTests/scenarios/CustomTemplate/runtest.ps1:364

This assertion checks a custom text file, not a workflow file; the comment is misleading.

# Check that legacy workflow file is present in final repository

 $projects = @(GetProjectsFromRepository -baseFolder $baseFolder -projectsFromSettings $repoSettings.projects)

-$filesToInclude, $filesToExclude = GetFilesToUpdate -settings $repoSettings -projects $projects -baseFolder $baseFolder -templateFolder $templateFolder -originalTemplateFolder $originalTemplateFolder
+$filesToInclude, $filesToExclude, $filesToRemove = GetFilesToUpdate -settings $repoSettings -projects $projects -baseFolder $baseFolder -templateFolder $templateFolder -templateSettings $templateRepoSettings -originalTemplateFolder $originalTemplateFolder


OleWunschmann · 2026-07-23T19:52:23Z

    }

+    It 'ResolveFilePaths skips files in folder whose name starts with source folder name' {
+        # Create a external file in folder whose name starts with the same prefix as sourceFolder


OleWunschmann · 2026-07-23T19:52:31Z

+
+        $filesToInclude, $filesToExclude, $filesToRemove = GetFilesToUpdate -settings $settings -baseFolder $baseFolder -templateFolder $templateFolder
+
+        # filesToRemove should one entry resolved from the base folder


OleWunschmann · 2026-07-23T19:52:38Z

+(Join-Path (Get-Location) $customWorkflowfileRelativePath) | Should -Exist
+Get-ContentLF -Path (Join-Path (Get-Location) $customWorkflowfileRelativePath) | Should -Be $finalRepoCustomWorkflowContent.Replace("`r", "").TrimEnd("`n")
+
+# Check that default custom file is NOT present (in repos's filesToExclude and template's filesToInclude)


Copilot

Pull request overview

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

Comments suppressed due to low confidence (2)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1171

$settings is already the effective result of ReadSettings, which includes the consumer's cached .github/AL-Go-TemplateRepoSettings.doNotEdit.json. Appending it after the live $templateSettings therefore reintroduces stale template entries. If a custom template removes or changes an include/exclude/remove entry, the old entry remains active for this run (and a stale filesToRemove can still win), so the change still requires a second update. Pass consumer-only settings here, or let ReadSettings skip the cached template settings when live template settings are supplied.

    if ($null -ne $templateSettings) {
        $filesToIncludeUnresolved += $templateSettings.customALGoFiles.filesToInclude
    }
    $filesToIncludeUnresolved += $settings.customALGoFiles.filesToInclude

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1202

Template-resolved entries can construct destinationFullPath from destinationFolder/destinationName without checking that the result remains under $baseFolder. For example, a matching template file with a ../ destination can enter $filesToRemove, after which CheckForUpdates.ps1 resolves and removes that path. The source-prefix check in ResolveFilePaths does not protect the destination. Canonicalize every removal destination and reject it unless it is within the repository root.

    $filesToRemove =  @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    if ($hasOriginalTemplate) {
        $filesToRemove += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    }
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

OleWunschmann · 2026-07-24T12:09:41Z

+
+The `customALGoFiles` setting of a custom template was only applied on the next Update (from `AL-Go-TemplateRepoSettings.doNotEdit.json`). Now the up-to-date settings of the custom template are used directly during "Update AL-Go System Files". The template's `filesToInclude`, `filesToExclude`, and `filesToRemove` settings are merged with the consumer repo's settings before resolution.
+
+- **`filesToInclude`** now also resolves files from the original AL-Go template. Files present in the official template that are not overridden by your custom template are propagated to consumer repos. When a file exists in both, the custom template version takes precedence.


Copilot

Pull request overview

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

Comments suppressed due to low confidence (3)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1210

Validate every resolved removal destination against the canonical $baseFolder boundary. A filesToRemove entry whose destinationFolder or destinationName contains .. can be resolved from a matching template file into a path outside the repository because ResolveFilePaths checks only the source path. That path is subsequently accepted by CheckForUpdates.ps1 and passed to Remove-Item, enabling deletion outside the cloned repository.

    $filesToRemove =  @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    if ($hasOriginalTemplate) {
        $filesToRemove += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    }
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

e2eTests/scenarios/CustomTemplate/runtest.ps1:454

Use the possessive “repo's,” not “repos's.”

# Check that optional custom file is present (in repos's filesToInclude)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:830

Appending a separator does not make the containment check path-safe: line 885 still uses case-insensitive, wildcard-aware -like. On Linux, sourceFolder = ../Repo can therefore pass the check for a base folder named repo, even though /tmp/Repo is a distinct sibling; paths containing [ or ? are also interpreted as patterns. Canonicalize both paths and use a platform-appropriate ordinal prefix comparison (and a literal path for enumeration).

    $sourceFolder = Join-Path $sourceFolder '' # Ensure source folder has a trailing slash for correct path resolution

OleWunschmann · 2026-07-24T13:33:31Z

+    UpdateCustomTemplateRepoSettingsSnapshot -baseFolder $baseFolder -templateFolder $templateFolder
+    $repoSettings = ReadSettings -buildMode '' -project '' -workflowName '' -userName '' -branchName '' -trigger '' | ConvertTo-HashTable -recurse


OleWunschmann · 2026-07-24T13:33:21Z

    # Send telemetery about customALGoFiles usage
    if ($settings.customALGoFiles.filesToInclude.Count -gt 0) {
-        Trace-Information -Message "Usage: Custom AL-Go Files (Include)"
+        Trace-Information -Message "Usage: Custom AL-Go Files (Include) of repository"
    }
    if ($settings.customALGoFiles.filesToExclude.Count -gt 0) {
-        Trace-Information -Message "Usage: Custom AL-Go Files (Exclude)"
+        Trace-Information -Message "Usage: Custom AL-Go Files (Exclude) of repository"
+    }
+    if ($settings.customALGoFiles.filesToRemove.Count -gt 0) {
+        Trace-Information -Message "Usage: Custom AL-Go Files (Remove) of repository"


Fixed by removing the "of repository"

Copilot

Pull request overview

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

Comments suppressed due to low confidence (3)

Actions/CheckForUpdates/CheckForUpdates.ps1:124

Refreshing the tracked snapshot in the comparison checkout makes it invisible to the update. GetFilesToUpdate later reads the same template file and compares it with this already-overwritten destination, so no $updateFiles entry is created; CloneIntoNewFolder then clones the stale remote snapshot and never writes the refreshed content. The new E2E assertion at runtest.ps1:400 will therefore fail, and other workflows continue reading stale template settings. Merge the fresh settings in memory, or explicitly carry the snapshot into the cloned update folder.

    UpdateCustomTemplateRepoSettingsSnapshot -baseFolder $baseFolder -templateFolder $templateFolder
    $repoSettings = ReadSettings -buildMode '' -project '' -workflowName '' -userName '' -branchName '' -trigger '' | ConvertTo-HashTable -recurse

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1210

These newly resolved removal entries can point outside $baseFolder: a template-controlled destinationFolder or destinationName containing .. is used to construct destinationFullPath without a destination-boundary check. If the corresponding template source exists, CheckForUpdates later resolves and removes that path, allowing deletion outside the cloned repository (or causing the update to fail). Canonicalize each destination and reject any path outside the repository root before adding it to filesToRemove.

    $filesToRemove =  @(ResolveFilePaths -sourceFolder $templateFolder -originalSourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    if ($hasOriginalTemplate) {
        $filesToRemove += @(ResolveFilePaths -sourceFolder $originalTemplateFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)
    }
    $filesToRemove += @(ResolveFilePathsInDestinationFolder -destinationFolder $baseFolder -files $filesToRemoveUnresolved -projects $projects)

Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1:1178

At this point ReadSettings has already merged custom-template and consumer-repository arrays, so a template-only include triggers the “of repository” event and no template-specific telemetry is emitted. This does not provide the separate repository/template usage tracking described by the PR. Preserve the two sources until telemetry is recorded (or emit template telemetry before merging).

        Trace-Information -Message "Usage: Custom AL-Go Files (Include) of repository"
    }
    if ($settings.customALGoFiles.filesToExclude.Count -gt 0) {
        Trace-Information -Message "Usage: Custom AL-Go Files (Exclude) of repository"

Copilot

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

-# Remove files that are in $filesToExclude and exist in the repository
-$removeFiles = $filesToExclude | Where-Object { $_ -and (Test-Path -Path $_.destinationFullPath -PathType Leaf) } | ForEach-Object {
+# Remove files that are in $filesToExclude or $filesToRemove and exist in the repository
+$removeFiles = @($filesToExclude) + @($filesToRemove) | Where-Object { $_ -and (Test-Path -Path $_.destinationFullPath -PathType Leaf) } | ForEach-Object {


    - originalSourceFullPath: The full path to the original source file in the original template repository (if any).
+      Always $null for filesToRemove entries.


+# Check that missing workflow file is present (in default filesToExclude)
+(Join-Path (Get-Location) $missingWorkflowFileRelativePath) | Should -Exist


Enhance customALGoFiles feature (#3)

0d9e05e

Copilot AI review requested due to automatic review settings June 3, 2026 15:24

OleWunschmann requested a review from a team as a code owner June 3, 2026 15:24

Copilot AI reviewed Jun 3, 2026

View reviewed changes

OleWunschmann added 2 commits June 3, 2026 17:35

fixed typo

73f4ef3

fixed function description

bb38962

mazhelez requested a review from Copilot June 8, 2026 09:25

Copilot started reviewing on behalf of mazhelez June 8, 2026 09:25 View session

Copilot AI reviewed Jun 8, 2026

View reviewed changes

OleWunschmann and others added 2 commits June 9, 2026 18:17

Fixed tests for ps5 and string-prefix check for folder traversal

50ad11c

Merge branch 'main' into enhance-customALGoFiles-feature

7aa8766

OleWunschmann and others added 5 commits June 12, 2026 11:12

Merge branch 'main' into enhance-customALGoFiles-feature

f7496cc

Merge branch 'main' into enhance-customALGoFiles-feature

11e2efc

Merge branch 'main' into enhance-customALGoFiles-feature

b021013

Merge branch 'main' into enhance-customALGoFiles-feature

025747e

Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…

dd1771a

…es-feature

spetersenms reviewed Jul 7, 2026

View reviewed changes

Comment thread RELEASENOTES.md

spetersenms reviewed Jul 7, 2026

View reviewed changes

Comment thread RELEASENOTES.md

Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…

2d24972

…es-feature

OleWunschmann requested a review from spetersenms July 9, 2026 17:11

OleWunschmann added 2 commits July 14, 2026 18:27

Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…

5976abe

…es-feature

Extended settings schema and documentation for "destinationName"

7fa3522

mazhelez reviewed Jul 15, 2026

View reviewed changes

OleWunschmann added 2 commits July 20, 2026 16:13

Merge branch 'main' into enhance-customALGoFiles-feature

a5c5fb1

Merge branch 'main' into enhance-customALGoFiles-feature

181080e

Copilot AI review requested due to automatic review settings July 21, 2026 09:45

Copilot started reviewing on behalf of OleWunschmann July 21, 2026 09:46 View session

Copilot AI reviewed Jul 21, 2026

View reviewed changes

mazhelez self-assigned this Jul 21, 2026

Merge branch 'main' into enhance-customALGoFiles-feature

c23a8ae

Copilot AI review requested due to automatic review settings July 21, 2026 18:43

Copilot started reviewing on behalf of OleWunschmann July 21, 2026 18:43 View session

Copilot AI reviewed Jul 21, 2026

View reviewed changes

Potential fix for pull request finding

afce6d7

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings July 23, 2026 09:52

Copilot started reviewing on behalf of OleWunschmann July 23, 2026 09:52 View session

Copilot AI reviewed Jul 23, 2026

View reviewed changes

Fixed copilot review comments

00d1902

Copilot AI review requested due to automatic review settings July 23, 2026 19:52

Merge branch 'main' into enhance-customALGoFiles-feature

ee510bd

Copilot started reviewing on behalf of OleWunschmann July 23, 2026 19:52 View session

Copilot AI reviewed Jul 23, 2026

View reviewed changes

Fix copilot review comments

c8ded0d

Copilot AI review requested due to automatic review settings July 24, 2026 12:09

Copilot started reviewing on behalf of OleWunschmann July 24, 2026 12:10 View session

Cleanup

409371e

Copilot AI reviewed Jul 24, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings July 24, 2026 12:15

Copilot started reviewing on behalf of OleWunschmann July 24, 2026 12:16 View session

Copilot AI reviewed Jul 24, 2026

View reviewed changes

OleWunschmann added 2 commits July 24, 2026 14:24

Cleanup

84a656e

Fix copilot review comments

8682d62

Copilot AI review requested due to automatic review settings July 24, 2026 13:32

Copilot started reviewing on behalf of OleWunschmann July 24, 2026 13:33 View session

Copilot AI reviewed Jul 24, 2026

View reviewed changes

		$removeFiles = @($filesToExclude) + @($filesToRemove) \| Where-Object { $_ -and (Test-Path -Path $_.destinationFullPath -PathType Leaf) } \| ForEach-Object {
		$relativePath = Resolve-Path -Path $_.destinationFullPath -Relative


		$filesToInclude, $filesToExclude, $filesToRemove = GetFilesToUpdate -settings $settings -baseFolder $baseFolder -templateFolder $templateFolder

		# filesToRemove should one entry resolved from the base folder


		The `customALGoFiles` setting of a custom template was only applied on the next Update (from `AL-Go-TemplateRepoSettings.doNotEdit.json`). Now the up-to-date settings of the custom template are used directly during "Update AL-Go System Files". The template's `filesToInclude`, `filesToExclude`, and `filesToRemove` settings are merged with the consumer repo's settings before resolution.

		- `filesToInclude` now also resolves files from the original AL-Go template. Files present in the official template that are not overridden by your custom template are propagated to consumer repos. When a file exists in both, the custom template version takes precedence.

		UpdateCustomTemplateRepoSettingsSnapshot -baseFolder $baseFolder -templateFolder $templateFolder
		$repoSettings = ReadSettings -buildMode '' -project '' -workflowName '' -userName '' -branchName '' -trigger '' \| ConvertTo-HashTable -recurse

		- originalSourceFullPath: The full path to the original source file in the original template repository (if any).
		Always $null for filesToRemove entries.

		# Check that missing workflow file is present (in default filesToExclude)
		(Join-Path (Get-Location) $missingWorkflowFileRelativePath) \| Should -Exist

Uh oh!

Conversation

OleWunschmann commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❔What, Why & How

✅ Checklist

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

OleWunschmann commented Jun 9, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

OleWunschmann commented Jun 3, 2026 •

edited

Loading