What's New in AL-Go for GitHub: Introducing Custom Templates (2025 release wave 2)
AL-Go for GitHub custom templates and custom jobs: how a custom template repository sits between the original AL-Go template and end repositories, propagates jobs and settings, and what limits apply. Mentions custom jobs from AL-Go 7.3 and a naming rule.
- Introduction and customization philosophy
- Existing customization methods
- Custom jobs in AL-Go
- Custom templates concept and architecture
- Custom templates demo and walkthrough
- Custom jobs support and limitations
- Custom templates support and limitations
- Resources and conclusion
Overview
The video covers customization options in AL-Go for GitHub, the DevOps solution for Business Central development. It recaps existing ways to customize, then describes custom jobs, which let you inject YAML into workflows supplied by AL-Go. Custom jobs are available from the 7.3 release.
It then introduces custom templates: a custom template is itself an AL-Go repository that works as a middle layer between the original AL-Go template and end repositories. Custom jobs and settings defined there propagate to repositories that reference the template. The video includes a demo and walks through the limitations, including that native workflows cannot be removed or changed and that the update behavior may change after feedback.
Key points
- Custom jobs, available from AL-Go 7.3, add jobs to existing AL-Go workflows by injecting YAML.
- Custom jobs must be prefixed with ‘custom job’ to avoid conflicts with future native jobs.
- A custom template is an AL-Go repository that sits between the original AL-Go template and end repositories.
- Custom settings in a custom template reach end repositories through a new settings file, only for repositories that reference the template.
- Native AL-Go workflows cannot be removed or changed, apart from adding custom jobs.
- AL-Go actions used in custom jobs are not updated when you run update AL-Go system files.
- Non-AL-Go files and custom templates are not updated by that run; the presenter says this may change after feedback.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Custom templates for AL-Go | 2:00 |
| Custom jobs in AL-Go workflows | 1:36 |
| Settings propagation in custom templates | 2:42 |
| Native job dependencies with custom jobs | 5:22 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
Quotes
- 0:17 “Ago for GitHub is a plug-and-play DevOps solutions for business central development that aims to cover 90% of the functionality that 100% of the”
- 1:36 “From the 7.3 release of AOG Go, there’s actually a new way to customize AOGO. Namely, this is the support for adding custom jobs”
- 2:42 “with the support of custom templates, we add a middle layer uh a custom template layer that is actually an ago repository itself and”
- 5:05 “we introduced a new naming convention, namely custom jobs must be prefixed with custom job.”
- 5:50 “AOG actions used in custom jobs will not be updated when you run update AOG system files.”
- 6:35 “native Aogo workflows cannot be removed or changed apart from adding custom jobs of course.”
Disclaimers in the video
- 7:07 subject-to-change: For now nonaoggo files and custom templates are not updated when running update AOG system files. We have actually already received feedback so we might be changing this in the future.
Presenters (as heard): Maria Jallesa.