GitHub

Mon, 01 Jan 0001 00:00:00 +0000

There are two main approaches to running ALCops in GitHub: using AL-Go for GitHub (the recommended path) or building your own GitHub Actions workflow.

AL-Go for GitHub

AL-Go for GitHub has built-in support for custom code analyzers through its settings file.

Add the customCodeCops property to your AL-Go settings.json (typically .github/AL-Go-Settings.json or the project-level settings file):

{
 "enableCodeCop": true,
 "customCodeCops": [
 ".alcops/ALCops.ApplicationCop.dll",
 ".alcops/ALCops.DocumentationCop.dll",
 ".alcops/ALCops.FormattingCop.dll",
 ".alcops/ALCops.LinterCop.dll",
 ".alcops/ALCops.PlatformCop.dll",
 ".alcops/ALCops.TestAutomationCop.dll",
 ".alcops/ALCops.Common.dll"
 ]
}

AL-Go downloads the DLLs at build time and passes them to the compiler automatically. For a full list of AL-Go settings, see the AL-Go advanced settings reference .

Azure DevOps

Mon, 01 Jan 0001 00:00:00 +0000

Coming Soon

We are developing a dedicated ALCops extension for Azure DevOps that simplifies analyzer integration in your pipelines. This page will be updated with setup instructions when the extension is available.

CI/CD Pipelines on ALCops

GitHub

AL-Go for GitHub

Azure DevOps