RepoMicrosoftMicrosoftpublished Oct 5, 2021seen 1d

microsoft/AL-Go

PowerShell

Open original ↗

Captured source

source ↗
published Oct 5, 2021seen 1dcaptured 14hhttp 200method plain

microsoft/AL-Go

Description: The plug-and-play DevOps solution for Business Central app development on GitHub

Language: PowerShell

License: MIT

Stars: 480

Forks: 196

Open issues: 61

Created: 2021-10-05T11:46:26Z

Pushed: 2026-06-10T10:58:54Z

Default branch: main

Fork: no

Archived: no

README:

AL-Go for GitHub

AL-Go for GitHub is a set of GitHub templates and actions, which can be used to setup and maintain professional DevOps processes for your Business Central AL projects.

The goal is that people who have created their GitHub repositories based on the AL-Go templates, can maintain these repositories and stay current just by running a workflow, which updates their repositories. This includes necessary changes to scripts and workflows to cope with new features and functions in Business Central.

The roadmap for AL-Go for GitHub can be found here: https://aka.ms/ALGoRoadmap

Release notes for all versions of AL-Go for GitHub can be found [here](./RELEASENOTES.md).

Deprecations for all versions of AL-Go for GitHub can be found [here](./DEPRECATIONS.md).

The template repositories to use as starting point are:

AL-Go Workshop

Try out the AL-Go workshop for an in-depth workshop on AL-Go for GitHub functionality or examine the below usage scenarios, which explains how to get started and how to perform the most common tasks.

Usage scenarios

1. [Create a new per-tenant extension (like AL-Go) and start developing in VS Code](Scenarios/GetStarted.md) 1. [Add a test app to an existing project](Scenarios/AddATestApp.md) 1. [Register a customer sandbox environment for Continuous Deployment using S2S](Scenarios/RegisterSandboxEnvironment.md) 1. [Create a release of your application](Scenarios/CreateRelease.md) 1. [Register a customer production environment for Manual Deployment](Scenarios/RegisterProductionEnvironment.md) 1. [Create a GhTokenWorkflow secret](Scenarios/GhTokenWorkflow.md) 1. [Update AL-Go system files](Scenarios/UpdateAlGoSystemFiles.md) 1. [Use Azure KeyVault for secrets with AL-Go](Scenarios/UseAzureKeyVault.md) 1. [Create Online Development Environment from VS Code](Scenarios/CreateOnlineDevEnv.md) 1. [Create Online Development Environment from GitHub](Scenarios/CreateOnlineDevEnv2.md) 1. [Set up CI/CD for an existing per tenant extension (BingMaps)](Scenarios/SetupCiCdForExistingPTE.md) 1. [Set up CI/CD for an existing AppSource App](Scenarios/SetupCiCdForExistingAppSourceApp.md) 1. [Enable KeyVault access for your AppSource App during development and/or tests](Scenarios/EnableKeyVaultForAppSourceApp.md) 1. [Set up your own GitHub runner to increase build performance](Scenarios/SelfHostedGitHubRunner.md) 1. [Introducing a dependency to another GitHub repository](Scenarios/AppDependencies.md) 1. [DeliveryTargets and NuGet/GitHub Packages](Scenarios/DeliveryTargets.md) 1. [Enabling Telemetry for AL-Go workflows and actions](Scenarios/EnablingTelemetry.md) 1. [Add a performance test app to an existing project](Scenarios/AddAPerformanceTestApp.md) 1. [Publish your app to AppSource](Scenarios/PublishToAppSource.md) 1. [Connect your GitHub repository to Power Platform](Scenarios/SetupPowerPlatform.md) 1. [How to set up Service Principal for Power Platform](Scenarios/SetupServicePrincipalForPowerPlatform.md) 1. [Try one of the Business Central and Power Platform samples](Scenarios/TryPowerPlatformSamples.md) 1. [Customizing AL-Go for GitHub](Scenarios/CustomizingALGoForGitHub.md)

Migration scenarios

A. [Migrate a repository from Azure DevOps to AL-Go for GitHub without history](Scenarios/MigrateFromAzureDevOpsWithoutHistory.md)

B. [Migrate a repository from Azure DevOps to AL-Go for GitHub with history](Scenarios/MigrateFromAzureDevOpsWithHistory.md)

> [!NOTE] > Please refer to [this description](Scenarios/settings.md) to learn about the settings file and how you can modify default behaviors.

This project

This project is the main source repository for AL-Go for GitHub. This project is deployed on every release to a branch in the following repositories:

Contributing

Please read [this document](Scenarios/Contribute.md) to understand how to contribute to AL-Go for GitHub.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

See also

Excerpt shown — open the source for the full document.