Use the setting "customALGoFiles" from the custom template settings when updating

[OleWunschmann]

Idea Description

If a custom AL-Go template contains files outside the default directories or uses non-standard file extensions, you can include them by setting "customALGoFiles"."filesToInclude".

The current problem: when you change that setting in the custom template, the first update workflow run does not pick up the new value. The first run only writes the template repo settings into .github/AL-Go-TemplateRepoSettings.doNotEdit.json. Only on a second run does the workflow read that file and include the new filesToInclude value. In practice this causes two CI/CD runs for a single change.

Can the update workflow be adjusted to include the new template repository values during the same update run?

Proposed change:

• Modify Actions\CheckForUpdates\CheckForUpdates.ps1:

  • Pass the $templateRepoSettings object into the GetFilesToUpdate function.

• Modify Actions\CheckForUpdates\CheckForUpdates.HelperFunctions.ps1, function GetFilesToUpdate:

  • Before merging files from $settings, add "customALGoFiles"."filesToInclude" from the passed $templateRepoSettings into $filesToInclude.
  • Similarly, add "customALGoFiles"."filesToExclude" from $templateRepoSettings into $filesToExclude.

Alternatively, instead of passing the entire $templateRepoSettings object into GetFilesToUpdate, we could pass only the custom include/exclude file lists to that function.

This ensures the new custom file inclusion/exclusion values are considered immediately and prevents the need for a second CI/CD run.

Contribution (Optional)

• I would be open to contributing to this idea (implementation, documentation, testing, etc.)

[mazhelez]

Go for it!

[OleWunschmann]

While implementing the changes for this discussion, I found some issues and other features that would enhance the "customALGoFiles" feature.

I created the PR #2273.
Sadly I'm not able to directly request a review from you.