Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
97 commits
Select commit Hold shift + click to select a range
0d9e05e
Enhance customALGoFiles feature (#3)
OleWunschmann Jun 3, 2026
73f4ef3
fixed typo
OleWunschmann Jun 3, 2026
bb38962
fixed function description
OleWunschmann Jun 3, 2026
50ad11c
Fixed tests for ps5 and string-prefix check for folder traversal
OleWunschmann Jun 9, 2026
7aa8766
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jun 9, 2026
f7496cc
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jun 12, 2026
11e2efc
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jun 16, 2026
b021013
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jun 17, 2026
025747e
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jun 22, 2026
dd1771a
Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…
OleWunschmann Jun 30, 2026
2d24972
Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…
OleWunschmann Jul 9, 2026
5976abe
Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…
OleWunschmann Jul 14, 2026
7fa3522
Extended settings schema and documentation for "destinationName"
OleWunschmann Jul 14, 2026
a5c5fb1
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jul 20, 2026
181080e
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jul 21, 2026
c23a8ae
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jul 21, 2026
afce6d7
Potential fix for pull request finding
OleWunschmann Jul 23, 2026
00d1902
Fixed copilot review comments
OleWunschmann Jul 23, 2026
ee510bd
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jul 23, 2026
c8ded0d
Fix copilot review comments
OleWunschmann Jul 24, 2026
409371e
Cleanup
OleWunschmann Jul 24, 2026
84a656e
Cleanup
OleWunschmann Jul 24, 2026
8682d62
Fix copilot review comments
OleWunschmann Jul 24, 2026
051d08a
Remove support for fileToRemove
OleWunschmann Jul 29, 2026
1a037b8
Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…
OleWunschmann Jul 29, 2026
d412a75
Fixed copilot review comment
OleWunschmann Jul 29, 2026
6376e16
Fixed issues
OleWunschmann Jul 29, 2026
73e159c
Cleanup
OleWunschmann Jul 29, 2026
cf71143
Fixed boundary escape for destinationFolder and destinationName
OleWunschmann Jul 29, 2026
f94fe4e
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Jul 31, 2026
61c640d
Fixed boundary escape for destinationName and typos
OleWunschmann Jul 31, 2026
ea2688e
Fixed boundry escape for wildcards and for linux
OleWunschmann Jul 31, 2026
aab09ca
Merge branch 'main' into enhance-customALGoFiles-feature
aholstrup1 Aug 12, 2026
0747977
Merge branch 'main' into enhance-customALGoFiles-feature
aholstrup1 Aug 14, 2026
fb60e90
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Aug 28, 2026
14ca702
Fix path comparisons with OS specific casings
OleWunschmann Sep 1, 2026
fd18fd4
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Sep 1, 2026
95d9cf4
Resolve symlinks/junctions
OleWunschmann Sep 15, 2026
d8495f7
Merge remote-tracking branch 'origin/main' into enhance-customALGoFil…
OleWunschmann Sep 15, 2026
684ae30
Fix copilot review comments
OleWunschmann Sep 16, 2026
6b0714b
Fix copilot review comment
OleWunschmann Sep 16, 2026
b7e2cd8
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Sep 18, 2026
448f661
Merge branch 'main' into enhance-customALGoFiles-feature
mazhelez Sep 18, 2026
2f41252
Merge branch 'main' into enhance-customALGoFiles-feature
mazhelez Sep 22, 2026
46293f7
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Sep 23, 2026
5d945c0
fix dangling links
OleWunschmann Sep 23, 2026
b42c085
reworked symlink/junction handling
OleWunschmann Sep 23, 2026
cf8671f
reworked symlink/junction handling and tests
OleWunschmann Sep 24, 2026
d9759ed
more rework
OleWunschmann Sep 24, 2026
65911f2
add tests for template settings snapshot
OleWunschmann Sep 24, 2026
d8e4b54
read settings without context, handle path issues, cleanup
OleWunschmann Sep 25, 2026
ff032bd
fixed issues with literal paths, symlinks/junctions and case-sensitivity
OleWunschmann Sep 25, 2026
a1a20dc
Fix typo in comment for clarity
OleWunschmann Sep 25, 2026
0b9dc8c
fix review comments
OleWunschmann Sep 25, 2026
a23d1fb
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Sep 30, 2026
60a175c
Fix review comments
OleWunschmann Sep 30, 2026
f9f9eb1
Fix review comments
OleWunschmann Sep 30, 2026
c54f757
fix e2e test
OleWunschmann Sep 30, 2026
fb139d9
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 6, 2026
dc0dd03
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 7, 2026
b52380d
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 8, 2026
5b542b5
fix resolve of relative file symlinks
OleWunschmann Oct 8, 2026
9c867e2
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 9, 2026
0887510
updated docu and releasenotes
OleWunschmann Oct 9, 2026
4bab4c5
fix PS5 tests
OleWunschmann Oct 12, 2026
d5a3ea5
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 12, 2026
8d973d2
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 15, 2026
02d1e6c
Guard repository settings updates against redirects
OleWunschmann Oct 15, 2026
8660f72
Update file resolution and destination handling in AL-Go
OleWunschmann Oct 15, 2026
04824bc
Update file resolution and destination handling docu
OleWunschmann Oct 15, 2026
6ecaf7c
Merge branch 'enhance-customALGoFiles-feature' of https://github.com/…
OleWunschmann Oct 15, 2026
028c8a3
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 21, 2026
3358cad
fix: abort AL-Go updates on unsafe or unverifiable paths
OleWunschmann Oct 21, 2026
70f9ef2
Updated releasenotes
OleWunschmann Oct 21, 2026
b022a00
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 21, 2026
b88bb07
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 22, 2026
6c9395f
fix: allow dot segments in per-project update paths
OleWunschmann Oct 22, 2026
b5bbb7f
fix: use refreshed repository settings for workflow dependency depth
OleWunschmann Oct 22, 2026
1ca4740
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Oct 31, 2026
553f998
reworked snapshot handling
OleWunschmann Oct 31, 2026
6681051
fix script analzer issues
OleWunschmann Oct 31, 2026
4964322
Update note on custom template settings refresh
OleWunschmann Oct 31, 2026
a4254fe
Assert physical equality for excluded files
OleWunschmann Oct 31, 2026
6a789ba
extended tests for redirected exclude files
OleWunschmann Oct 31, 2026
f07ba9a
Merge branch 'main' into enhance-customALGoFiles-feature
mazhelez Nov 4, 2026
0a6ae9d
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Nov 11, 2026
7efc330
Fix copilot review comments
OleWunschmann Nov 11, 2026
d6a20f7
Update AL-Go System Files with custom template settings
OleWunschmann Nov 11, 2026
ff5564a
Updated releasenotes
OleWunschmann Nov 11, 2026
1e9e5cd
Restore case-insensitive matching for deprecated unusedALGoSystemFile…
OleWunschmann Nov 11, 2026
5a4b361
Add physical path validation for template source folders
OleWunschmann Nov 11, 2026
787ea74
Fix wildcard expansion in helper function settings paths
OleWunschmann Nov 11, 2026
e8dbda6
Fix e2e test
OleWunschmann Nov 12, 2026
22c0731
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Nov 12, 2026
1df7e9c
Improve helper documentation
OleWunschmann Nov 13, 2026
5b6b770
Update description for filesToExclude in settings.schema.json
OleWunschmann Nov 13, 2026
025452d
Merge branch 'main' into enhance-customALGoFiles-feature
OleWunschmann Nov 18, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Actions/.Modules/settings.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -919,6 +919,7 @@
"type": "object",
"properties": {
"filesToInclude": {
"description": "An array of file specifications to include in the update. Files that match these specifications are copied from the template to the repository. When used in a custom template's settings, inclusions are also propagated from the original template to consumer repos even if the files no longer exist in the custom template.",
"type": "array",
"items": {
"type": "object",
Expand All @@ -935,6 +936,10 @@
"type": "string",
"description": "The destination folder where the files should be updated, relative to the repository root. If not specified, defaults to the same as the source file folder."
},
"destinationName": {
"type": "string",
"description": "The filename to use at the destination. If specified, overrides the source filename, allowing the file to be renamed when copied. Should be used together with a filter that matches a single file."
Comment thread
mazhelez marked this conversation as resolved.
Resolved
Comment thread
Copilot marked this conversation as resolved.
Resolved
},
"perProject": {
"type": "boolean",
"description": "Indicates whether the file update should be applied per project. In that case, the destinationFolder is considered relative to each project folder."
Expand All @@ -943,6 +948,7 @@
}
},
"filesToExclude": {
"description": "An array of file specifications to exclude from the update. Files that match these specifications are not copied from the template to the repository. Existing destination files selected for exclusion are removed unless another included source targets the same destination. When a custom template is in use, exclusion rules from the custom template or consumer repository settings are matched against files in both the custom template and the original AL-Go template.",
"type": "array",
"items": {
"type": "object",
Expand Down
2,756 changes: 1,552 additions & 1,204 deletions Actions/CheckForUpdates/CheckForUpdates.HelperFunctions.ps1

Large diffs are not rendered by default.

266 changes: 182 additions & 84 deletions Actions/CheckForUpdates/CheckForUpdates.ps1

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion Actions/CheckForUpdates/yamlclass.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ class Yaml {

# Static load function to load a Yaml file into a Yaml class
static [Yaml] Load([string] $filename) {
$fileContent = Get-Content -Path $filename -Encoding UTF8
$fileContent = Get-Content -LiteralPath $filename -Encoding UTF8
return [Yaml]::new($fileContent)
}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,9 @@ function CreateBuildDimensions {
Analyzes a folder for AL-Go projects and determines the build order of these projects.
The build order is determined by the project dependencies and the projects that have been modified.

.Parameter settings
Settings used to select projects. Defaults to the deserialized Settings environment variable.

.Outputs
The function returns the following values:
- projects: An array of all projects found in the folder
Expand All @@ -165,7 +168,9 @@ function Get-ProjectsToBuild {
[Parameter(HelpMessage = "An array of changed files paths, used to filter the projects to build", Mandatory = $false)]
[string[]] $modifiedFiles = @(),
[Parameter(HelpMessage = "The maximum depth to build the dependency tree", Mandatory = $false)]
[int] $maxBuildDepth = 0
[int] $maxBuildDepth = 0,
[Parameter(HelpMessage = "Settings used to select projects", Mandatory = $false)]
[hashtable] $settings = ($env:Settings | ConvertFrom-Json | ConvertTo-HashTable -recurse)
)

. (Join-Path -Path $PSScriptRoot -ChildPath "..\AL-Go-Helper.ps1" -Resolve)
Expand All @@ -174,7 +179,6 @@ function Get-ProjectsToBuild {

Push-Location $baseFolder
try {
$settings = $env:Settings | ConvertFrom-Json
$projects = @(GetProjectsFromRepository -baseFolder $baseFolder -projectsFromSettings $settings.projects)
Write-Host "Found AL-Go Projects: $($projects -join ', ')"

Expand Down
2 changes: 1 addition & 1 deletion Actions/Github-Helper.psm1
Original file line number Diff line number Diff line change
Expand Up @@ -857,7 +857,7 @@ function Get-ContentLF {
)

Process {
(Get-Content -Path $path -Encoding UTF8 -Raw).Replace("`r", "").TrimEnd("`n")
(Get-Content -LiteralPath $path -Encoding UTF8 -Raw).Replace("`r", "").TrimEnd("`n")
}
}

Expand Down
13 changes: 13 additions & 0 deletions RELEASENOTES.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,16 @@
### Improved file handling in Update AL-Go System Files

- Update AL-Go System Files now uses the latest repository settings from a custom template, such as `customALGoFiles`, in the same update rather than applying them on the next run.
- Workflow dependency depth is also determined using these refreshed settings, ensuring enough sequential build jobs are generated for the configured projects.
- Default AL-Go file rules and `customALGoFiles.filesToInclude` now also resolve files from the original AL-Go template when they are absent from the custom template; `filesToExclude` applies to these files too.
- **Breaking change:** standard workflows or scripts intentionally deleted from a custom template can be recreated in consumer repositories. To keep them absent, add matching `customALGoFiles.filesToExclude` entries to the custom template's `.github/AL-Go-Settings.json` before updating consumers.
- `filesToExclude` now respects destination mappings from `filesToInclude`, including renamed files and per-project destinations. Existing files are removed unless another included source targets the same destination.
- Use `destinationName` in `filesToInclude` to rename included files at the destination.
- Update AL-Go System Files now ignores trigger-based conditional settings when selecting files and generating workflows, including during CI/CD update checks.
- For safety, the update validates selected source paths before reading file contents and destination paths before writing or removing files. These operations are blocked when a path redirects through a symbolic link or junction, or its physical location cannot be verified.

See [Customizing AL-Go for GitHub](Scenarios/CustomizingALGoForGitHub.md#using-custom-template-files) for details.

### Optional draft PR build skipping

The new `skipDraftPullRequests` setting (default `false`) lets PTE and AppSource repositories skip AL-Go's built-in PR build jobs while a pull request is draft and build when it is marked ready for review. Custom jobs remain user-managed and are not modified. Default behavior and merge-queue builds are unchanged. Run **Update AL-Go System Files** after changing the setting. See [skipDraftPullRequests](Scenarios/settings.md#skipDraftPullRequests).
Expand Down
33 changes: 28 additions & 5 deletions Scenarios/CustomizingALGoForGitHub.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,31 +235,54 @@ In order to instruct AL-Go which files to look for at the template repository, y

`filesToInclude`, as the name suggests, is an array of file configurations that will instruct AL-Go which files to include (create/update). Every item in the array may contain the following properties:

- `sourceFolder`: A path to a folder, relative to the template, where to look for files. If not specified the root folder is implied. `*` characters are not supported. _Example_: `src/scripts`.
- `sourceFolder`: A literal path to a folder, relative to the template, where to look for files. If not specified the root folder is implied. Wildcards are not supported; characters such as `[` and `]` are treated literally. _Example_: `src/scripts`.
- `filter`: A string to use for filtering in the specified source path. It can contain `*` and `?` wildcards. _Example_: `*.ps1` or `fileToUpdate.ps1`.
- `destinationFolder`: A path to a folder, relative to repository that is being updated, where the files should be placed. If not specified, defaults to the same as the source file folder. _Example_: `src/templateScripts`.
- `perProject`: A boolean that indicates whether the matched files should be propagated for all available AL-Go projects. In that case, `destinationFolder` is relative to the project folder. _Example_: `.AL-Go/scripts`.
- `destinationName`: The filename to use at the destination. If specified, overrides the source filename, allowing the file to be renamed when copied. Should be used together with a `filter` that matches a single file. _Example_: `customScript.ps1`.

> [!NOTE]
> `filesToInclude` is used to define all the template files that will be used by AL-Go for GitHub. If a template file is not matched, it will be ignored. Please pay attention, when changing the file configurations: there might be template files that were previously propagated to your repositories. In case these files are no longer matched via `filesToInclude`, AL-Go for GitHub will ignore them and you might have to remove them manually.
> `filesToInclude` is used to define all the template files that will be used by AL-Go for GitHub. If a template file is not matched, it will be ignored. Files propagated by an earlier configuration are not automatically removed when they are no longer matched. For example, changing `destinationName` creates or updates the new filename but leaves the old filename in the consumer repository; remove the old file manually if it is no longer needed.

If multiple include rules target the same destination file, only the first eligible source is used. Custom template matches are considered before original template matches; within each template, default AL-Go file rules precede `customALGoFiles.filesToInclude` rules. A later rule with the same destination does not override the earlier one, including when `destinationName` creates the collision.

When using a custom template repository, `filesToInclude` also resolves files from the **original** AL-Go template (i.e. the official [AL-Go-PTE](https://github.com/microsoft/AL-Go-PTE) or [AL-Go-AppSource](https://github.com/microsoft/AL-Go-AppSource) template). This means files present in the official AL-Go template that are not overridden by your custom template are still propagated to consumer repositories. When a file exists in both the original template and your custom template, how the file's **content** is resolved depends on the file's type:

- **Workflow files** (`.github/workflows/*.yaml`/`*.yml`): the content is based on the original template's file, with customizations from your custom template's copy (see [Adding custom jobs](#adding-custom-jobs)) re-applied on top.
- **Settings files**: if the destination file already exists, its settings are preserved and only its `$schema` is updated from the original template. If it does not exist, the original template's settings are used. Current custom template repository settings are also read when updating workflows.
- **All other files** (e.g. PowerShell scripts, `.copy.md`, `.agent.md`): the original template's file content is used as-is; changes made to that same file in your custom template are not applied in this case.

The following table summarizes how `filesToInclude` resolves files when a custom template is in use:

| File is present in original template | File is present in custom template | File is matched by `filesToInclude` | Result |
|---|---|---|---|
| Yes | No | Yes | File from **original template** is propagated |
| No | Yes | Yes | File from **custom template** is propagated |
| Yes | Yes | Yes | File from **original template** is propagated; for Workflow files, customizations from the **custom template** are also applied |
| Yes/No | Yes/No | No | File is **ignored** |

`filesToExclude` is an array of file configurations that will instruct AL-Go which files to exclude (remove) from `filesToInclude`. Every item in the array may contain the following properties:

- `sourceFolder`: A path to a folder, relative to the template, where to look for files. If not specified the root folder is implied. _Example_: `src/scripts`.
- `filter`: A string to use for filtering in the specified source path. It can contain `*` and `?` wildcards. _Example_: `notRelevantScript.ps1` or `*-internal.ps1`

> [!NOTE] `filesToExclude` is an array of file configurations already included in `filesToInclude`. These files are specifically marked to be excluded from the update process.
> This mechanism allows for fine-grained control over which files are propagated to the end repository and which should be explicitly removed, ensuring that unwanted files are not carried forward during updates.
> Exclusions match source files, not destination filenames. If another included source targets the same destination, it is updated from that source instead of being removed. Exclusion rules can only match files still present in the custom or original template; removing a file from both templates does not make an existing consumer copy eligible for automatic removal.

> [!TIP]
> When using a custom template repository, you can use `filesToExclude` in the custom template's settings to prevent files from the original AL-Go template from being propagated to consumer repos. For example, if the original template includes a workflow you don't want in your consumer repos, adding it to `filesToExclude` in your custom template's settings will remove it during the next update, provided no other included source targets the same destination.

The following table summarizes how AL-Go for GitHub manages file updates and exclusions when using custom template files. Say, there is a file (e.g. `file.ps1`) in the template repository.

| File is present in end repo | File is matched by `filesToInclude` | File is matched by `filesToExclude` | Result |
|---|---|---|---|
| Yes/No | Yes | No | The file is **updated/created** in the end repo |
| Yes | Yes | Yes | The file is **removed** from the end repo, as it's matched for exclusion |
| Yes | No | Yes | The files is **_not_** removed as it was not matched as update |
| Yes | Yes | Yes | The file is **removed** from the end repo if no other included source targets the same destination; otherwise that source updates it |
| Yes | No | Yes | The file is **_not_** removed as it was not matched as update |
| No | Yes/No | Yes | The file is **_not_ created** in the end repo, as it's matched for exclusion |

For safety, files managed by Update AL-Go System Files must not use paths redirected through symlinks or junctions. Such paths cause update checks and updates to fail with an error.

### Examples of using custom template files

Below are examples of how to use the `filesToInclude` and `filesToExclude` settings in your AL-Go configuration.
Expand Down
4 changes: 3 additions & 1 deletion Scenarios/settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,8 @@ to your [project settings file](#where-are-the-settings-located) will ensure tha
- **users** settings will be applied for users matching the patterns
- **triggers** settings will be applied when `GITHUB_EVENT_NAME` matches values (for example `push`, `pull_request`, `schedule`, `workflow_dispatch`)

When updating AL-Go System Files, settings for selecting files are read without a build mode, project, workflow, user, branch, or trigger context. When generating each workflow, settings are read again with that workflow's name, so workflow-specific settings and conditions on that workflow apply. Neither read uses the event that triggered the update. Unconditional settings and conditions matching the repository still apply; conditions on other execution contexts do not apply.

**Note:** You can use `workflowDefaultInputs` within conditional settings to apply workflow input defaults only when certain conditions are met. For example, you could set different default values for specific workflows or branches.

You could imagine that you could have an organizational settings variable containing:
Expand Down Expand Up @@ -258,7 +260,7 @@ Please read the release notes carefully when installing new versions of AL-Go fo
| <a id="BcContainerHelperVersion"></a>BcContainerHelperVersion | This setting can be set to a specific version (ex. 3.0.8) of BcContainerHelper to force AL-Go to use this version. **latest** means that AL-Go will use the latest released version. **preview** means that AL-Go will use the latest preview version. **dev** means that AL-Go will use the dev branch of containerhelper. | latest (or preview for AL-Go preview) |
| <a id="unusedALGoSystemFiles"></a>unusedALGoSystemFiles (**deprecated**) | An array of AL-Go System Files, which won't be updated during Update AL-Go System Files. They will instead be removed.<br />Use this setting with care, as this can break the AL-Go for GitHub functionality and potentially leave your repo no longer functional. | [ ] |
| <a id="reportsuppresseddiagnostics"></a>reportSuppressedDiagnostics | If this setting is set to true, the AL compiler will report diagnostics which are suppressed in the code using the pragma `#pragma warning disable <id>`. This can be useful if you want to ensure that no warnings are suppressed in your code. | false |
| <a id="customALGoFiles"></a>customALGoFiles | An object to configure custom AL-Go files, that will be updated during "Update AL-Go System Files" workflow. The object can contain properties `filesToInclude` and `filesToExclude`. Read more at [Customizing AL-Go](CustomizingALGoForGitHub.md#Using-custom-template-files). | `{ "filesToInclude": [], "filesToExclude": [] }`
| <a id="customALGoFiles"></a>customALGoFiles | An object to configure custom AL-Go files, that will be updated during "Update AL-Go System Files" workflow. Read more at [Customizing AL-Go](CustomizingALGoForGitHub.md#Using-custom-template-files).<br />**filesToInclude** = an array of file specifications to include (create/update). Each item can contain **sourceFolder** (folder relative to the template root to look for files, default root folder), **filter** (filter string supporting `*` and `?` wildcards, default all files), **destinationFolder** (folder relative to the repository to place the files, default same as sourceFolder), **destinationName** (filename to use at the destination, overriding the source filename to rename the file when copied; should be used together with a filter matching a single file, default source filename), and **perProject** (boolean indicating whether the files should be propagated to all AL-Go projects, in which case destinationFolder is relative to the project folder, default false).<br />**filesToExclude** = an array of file specifications to exclude (remove) from `filesToInclude`. Each item can contain **sourceFolder** and **filter** (same meaning as above). | `{ "filesToInclude": [], "filesToExclude": [] }`

## Settings sources in workflow logs <a id="settings-sources"></a>

Expand Down
Loading