---
id: video/WU2fLjIQSuU
type: video
title: "What's New: AL Go for GitHub (2023 release wave 2)"
summary: "AL Go for GitHub 3.2 (2023 release wave 2): HSM code signing via Azure Key Vault, revamped deployment with DeployTo environment settings and custom deployment scripts (e.g. on-premises), a pull request status check job for branch protection, compiler folder builds on Linux runners without containers, and the use GH token workflow option. Settings locations and upgrading via Update AL Go system files are recapped (unchanged). A BCPT test result viewer and indirect template customization are only open PRs with no promises or dates."
tier: official
language: en
tags:
  - al-go
  - devops
  - ci-cd
  - github
  - settings
  - code signing
  - hsm
  - deployment
  - environments
  - versioning
  - custom deployment
  - on-premises
system: platform
review:
  state: reviewed
  by: opus
  at: "2026-10-07T23:13:45.300Z"
  flags: []
generated:
  at: "2026-10-07T23:13:45.361Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: b5cc382f40fce13bad7ad6f219215a5edbbc1f57e624cb4d06192e29f5680324
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=19s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 19
    quote: AL Go for GitHub is the plug-and-play DevOps solution for Business Central development on GitHub
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=59s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 59
    quote: You don't need any knowledge in Docker, PowerShell, or YAML, or anything like that. You don't need a dedicated DevOps engineer
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=241s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 241
    quote: There are three types of settings in AL Go for GitHub really. There's repository wide settings
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=465s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 465
    quote: AL Go for GitHub version 3.2
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=514s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 514
    quote: Every time you have a CI CD or build running, there'll be a job called check for updates
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=635s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 635
    quote: what we did in AL Go for GitHub was to add support for HSM key storage in Azure Key Vault
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=805s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 805
    quote: the real way of of doing this going forward is to create a new setting called deploy to an environment name, meaning deploy to
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=911s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 911
    quote: you can set it to true or false, no matter whether it's a it's a production environment or a um or a sandbox environment
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=950s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 950
    quote: the reason for that is really another newcomer in in this version, which is custom deployment
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1436s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1436
    quote: a new functionality that allows AL Go to build apps without containers, and allowed GitHub to cache artifacts
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1447s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1447
    quote: GitHub hosted runner Linux runners are half the price, and uh they are 33 approximately percent faster than the Windows runners
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1615s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1615
    quote: pulling generic image takes 4 minutes creating a container takes 7 minutes. So, 11 minutes of these 14 or 12 minutes actually goes for
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1650s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1650
    quote: this build actually took 4 minutes and 42 seconds. So, it's quite a bit faster, 12 minutes faster than the other build
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1650s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1650
    quote: we do not publish apps, use compiler folder, runs on Ubuntu and GitHub runner Ubuntu click actions and we'll see that this build actually
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1757s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1757
    quote: for a free skew of of GitHub, there's like 2,000 minutes included for free of of of runners. Uh that is that equals to
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1863s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 1863
    quote: GitHub says that triggering a workflow from a workflow is not possible using the GitHub token. Uh meaning that if we run a workflow
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2040s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2040
    quote: there's no promises, no dates. I know that it looks like everything is done, but we might still like pull the plug and say
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2201s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2201
    quote: I think 80% of partners would not need to, like, change anything. Uh they'd be able to use AL Go for GitHub as is
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2352s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2352
    quote: I've integrated this job into my CI/CD pipeline
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2479s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2479
    quote: added settings will also be transferred to the repo by update AL Go system files. If you already set the settings in this file,
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2566s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2566
    quote: if there is already a a a job with the same name in the repository that it comes from the indirect repository, it will
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2578s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2578
    quote: if you have like new jobs that are not named the same as as as jobs that are that are from AL Go or
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2635s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2635
    quote: you just you decide when you want to uptake new changes to that, and these changes can then be be transferred to uh to
  - kind: video
    url: https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2648s
    title: "What's New: AL Go for GitHub (2023 release wave 2)"
    date: "2023-12-20T08:03:42.000Z"
    commit: null
    t: 2648
    quote: you could also have a fork of AL Go. Uh there are different ways of doing that and and we're not sure whether we
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: WU2fLjIQSuU
channel: yt-microsoft
source_name: Microsoft Dynamics 365 Business Central (YouTube)
url: https://www.youtube.com/watch?v=WU2fLjIQSuU
published_at: "2023-12-20T08:03:42.000Z"
duration_s: 2682
captions: full
audience:
  - developer
  - administrator
  - functional consultant
chapters:
  - t: 0
    title: Introduction to AL Go for GitHub
  - t: 129
    title: Session topics and agenda
  - t: 203
    title: Settings and configuration types
  - t: 415
    title: Versioning and upgrades
  - t: 562
    title: Code signing and HSM key storage
  - t: 677
    title: Deployment enhancements and environments
  - t: 950
    title: Custom deployment mechanism and on-premises support
  - t: 1150
    title: Pull request status check and GitHub branch protection
  - t: 1300
    title: Compiler folder and Linux runner architecture
  - t: 1550
    title: Performance comparison and caching optimization
  - t: 1740
    title: Cost implications and GitHub minutes calculation
  - t: 1840
    title: Use GH token workflow feature
  - t: 2028
    title: BCPT test result viewer
  - t: 2190
    title: Customizing AL Go for GitHub with templates
features:
  - name: AL Go for GitHub DevOps solution
    status: unclear
    t: 19
    verified: false
    status_source: video
  - name: Settings configuration types
    status: unclear
    t: 203
    verified: false
    status_source: video
  - name: Version tracking in AL Go
    status: unclear
    t: 428
    verified: false
    status_source: video
  - name: Update AL Go system files workflow
    status: unclear
    t: 501
    verified: false
    status_source: video
  - name: HSM key storage for code signing
    status: unclear
    t: 577
    verified: false
    status_source: video
  - name: GitHub environments deployment
    status: unclear
    t: 688
    verified: false
    status_source: video
  - name: Deploy to environment configuration
    status: unclear
    t: 805
    verified: false
    status_source: video
  - name: Continuous deployment to production environments
    status: unclear
    t: 880
    verified: false
    status_source: video
  - name: Custom deployment mechanism
    status: unclear
    t: 950
    verified: false
    status_source: video
  - name: Custom GitHub runner support
    status: unclear
    t: 1049
    verified: false
    status_source: video
  - name: Pull request status check job
    status: unclear
    t: 1170
    verified: false
    status_source: video
  - name: Compiler folder feature
    status: unclear
    t: 1338
    verified: false
    status_source: video
  - name: Linux runner build optimization
    status: unclear
    t: 1485
    verified: false
    status_source: video
  - name: Business Central artifact caching
    status: unclear
    t: 1689
    verified: false
    status_source: video
  - name: Use GH token workflow feature
    status: unclear
    t: 1840
    verified: false
    status_source: video
  - name: BCPT test result viewer
    status: unclear
    t: 2053
    verified: false
    status_source: video
  - name: Customize AL Go for GitHub
    status: unclear
    t: 2190
    verified: false
    status_source: video
  - name: BC container partial script customization
    status: unclear
    t: 2389
    verified: false
    status_source: video
  - name: Indirect template repository for AL Go
    status: unclear
    t: 2452
    verified: false
    status_source: video
  - name: Custom job and step execution order
    status: unclear
    t: 2554
    verified: false
    status_source: video
  - name: Fork alternative for AL Go customization
    status: unclear
    t: 2648
    verified: false
    status_source: video
objects_mentioned:
  - other deploy to custom
  - other deploy to Q&A
  - other ALOps settings
  - other pull request handler
  - other run pipeline
  - other BCBT baseline.json
  - other BC container partial script
  - other custom job/my job
  - other custom job/prepare deploy
quotes:
  - t: 19
    text: AL Go for GitHub is the plug-and-play DevOps solution for Business Central development on GitHub
    check: exact
  - t: 59
    text: You don't need any knowledge in Docker, PowerShell, or YAML, or anything like that. You don't need a dedicated DevOps engineer
    check: exact
  - t: 241
    text: There are three types of settings in AL Go for GitHub really. There's repository wide settings
    check: exact
  - t: 465
    text: AL Go for GitHub version 3.2
    check: exact
  - t: 514
    text: Every time you have a CI CD or build running, there'll be a job called check for updates
    check: exact
  - t: 635
    text: what we did in AL Go for GitHub was to add support for HSM key storage in Azure Key Vault
    check: exact
  - t: 805
    text: the real way of of doing this going forward is to create a new setting called deploy to an environment name, meaning deploy to
    check: exact
  - t: 911
    text: you can set it to true or false, no matter whether it's a it's a production environment or a um or a sandbox environment
    check: exact
  - t: 950
    text: the reason for that is really another newcomer in in this version, which is custom deployment
    check: exact
  - t: 1436
    text: a new functionality that allows AL Go to build apps without containers, and allowed GitHub to cache artifacts
    check: exact
  - t: 1447
    text: GitHub hosted runner Linux runners are half the price, and uh they are 33 approximately percent faster than the Windows runners
    check: exact
  - t: 1615
    text: pulling generic image takes 4 minutes creating a container takes 7 minutes. So, 11 minutes of these 14 or 12 minutes actually goes for
    check: exact
  - t: 1650
    text: this build actually took 4 minutes and 42 seconds. So, it's quite a bit faster, 12 minutes faster than the other build
    check: exact
  - t: 1650
    text: we do not publish apps, use compiler folder, runs on Ubuntu and GitHub runner Ubuntu click actions and we'll see that this build actually
    check: exact
  - t: 1757
    text: for a free skew of of GitHub, there's like 2,000 minutes included for free of of of runners. Uh that is that equals to
    check: exact
  - t: 1863
    text: GitHub says that triggering a workflow from a workflow is not possible using the GitHub token. Uh meaning that if we run a workflow
    check: exact
  - t: 2040
    text: there's no promises, no dates. I know that it looks like everything is done, but we might still like pull the plug and say
    check: exact
  - t: 2201
    text: I think 80% of partners would not need to, like, change anything. Uh they'd be able to use AL Go for GitHub as is
    check: exact
  - t: 2352
    text: I've integrated this job into my CI/CD pipeline
    check: exact
  - t: 2479
    text: added settings will also be transferred to the repo by update AL Go system files. If you already set the settings in this file,
    check: exact
  - t: 2566
    text: if there is already a a a job with the same name in the repository that it comes from the indirect repository, it will
    check: exact
  - t: 2578
    text: if you have like new jobs that are not named the same as as as jobs that are that are from AL Go or
    check: exact
  - t: 2635
    text: you just you decide when you want to uptake new changes to that, and these changes can then be be transferred to uh to
    check: exact
  - t: 2648
    text: you could also have a fork of AL Go. Uh there are different ways of doing that and and we're not sure whether we
    check: exact
---

# What's New: AL Go for GitHub (2023 release wave 2)

> AL Go for GitHub 3.2 (2023 release wave 2): HSM code signing via Azure Key Vault, revamped deployment with DeployTo environment settings and custom deployment scripts (e.g. on-premises), a pull request status check job for branch protection, compiler folder builds on Linux runners without containers, and the use GH token workflow option. Settings locations and upgrading via Update AL Go system files are recapped (unchanged). A BCPT test result viewer and indirect template customization are only open PRs with no promises or dates.

[Watch on YouTube](https://www.youtube.com/watch?v=WU2fLjIQSuU) · Microsoft Dynamics 365 Business Central (YouTube) · 2023-12-20 · 44:42 · tier official · reviewed (checked by Opus)

## Overview

The session walks through what changed in AL Go for GitHub, the DevOps solution for Business Central development on GitHub. It covers settings levels, version tracking and upgrades, code signing with HSM-stored keys, and deployment changes such as a deploy to environment name setting and custom deployment scripts for non-SaaS targets.

It then covers build speed and cost: the compiler folder feature, building on Ubuntu runners without containers, and caching of Business Central artifacts. It ends with the GH token workflow option, a BCPT test result viewer that is still a draft pull request, and ways to customize AL Go through indirect template repositories. The presenters say they have not decided between templates and forks.

## Key points

- Three settings levels: repository-wide (template URL, schedules, runners, environments), project-wide (.AL-Go folder per project), and workflow-specific settings such as for test next minor/major. These are recapped, not changed.
- Upgrade with the Update AL Go system files workflow. It needs a secret named GH token workflow with a personal access token that can modify workflows. The version (e.g. 3.2) is shown in the initialize workflow output.
- Code signing: AL Go supports private keys in HSM key storage in Azure Key Vault, needed because certificate providers must deliver keys in hardware modules from July 1st.
- Deployment: a DeployTo<environment> setting (for example deploy to QA) replaces secret-based environment naming and covers environment type, branches, projects, sync mode, runs on and continuous deployment. Continuous deployment can be set true or false for any environment, including production.
- Custom deployment: setting a non-SaaS environment type runs your own .github/DeployTo<type>.ps1 script with passed parameters. Microsoft does not provide these scripts. A custom GitHub runner inside a firewall is optional.
- Linux build without containers needs do not publish apps and use compiler folder set to true, plus runs on and GitHub runner set to Ubuntu latest. Do not publish apps disables running tests. A build went from about 14.5 minutes to 4 min 42 s, then 3 min 38 s on a rebuild thanks to cached artifacts.
- A pull request status check job can serve as the required status check in GitHub branch protection, so you do not have to reference matrix jobs.

## Chapters

- [0:00](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=0s) Introduction to AL Go for GitHub
- [2:09](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=129s) Session topics and agenda
- [3:23](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=203s) Settings and configuration types
- [6:55](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=415s) Versioning and upgrades
- [9:22](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=562s) Code signing and HSM key storage
- [11:17](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=677s) Deployment enhancements and environments
- [15:50](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=950s) Custom deployment mechanism and on-premises support
- [19:10](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1150s) Pull request status check and GitHub branch protection
- [21:40](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1300s) Compiler folder and Linux runner architecture
- [25:50](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1550s) Performance comparison and caching optimization
- [29:00](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1740s) Cost implications and GitHub minutes calculation
- [30:40](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1840s) Use GH token workflow feature
- [33:48](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2028s) BCPT test result viewer
- [36:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2190s) Customizing AL Go for GitHub with templates

## Features

| Feature | Status | At |
|---|---|---|
| AL Go for GitHub DevOps solution | status not stated | [0:19](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=19s) |
| Settings configuration types | status not stated, demoed | [3:23](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=203s) |
| Version tracking in AL Go | status not stated, demoed | [7:08](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=428s) |
| Update AL Go system files workflow | status not stated | [8:21](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=501s) |
| HSM key storage for code signing | status not stated | [9:37](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=577s) |
| GitHub environments deployment | status not stated | [11:28](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=688s) |
| Deploy to environment configuration | status not stated, demoed | [13:25](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=805s) |
| Continuous deployment to production environments | status not stated | [14:40](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=880s) |
| Custom deployment mechanism | status not stated, demoed | [15:50](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=950s) |
| Custom GitHub runner support | status not stated | [17:29](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1049s) |
| Pull request status check job | status not stated, demoed | [19:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1170s) |
| Compiler folder feature | status not stated, demoed | [22:18](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1338s) |
| Linux runner build optimization | status not stated, demoed | [24:45](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1485s) |
| Business Central artifact caching | status not stated, demoed | [28:09](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1689s) |
| Use GH token workflow feature | status not stated, demoed | [30:40](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1840s) |
| BCPT test result viewer | status not stated, demoed | [34:13](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2053s) |
| Customize AL Go for GitHub | status not stated, demoed | [36:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2190s) |
| BC container partial script customization | status not stated, demoed | [39:49](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2389s) |
| Indirect template repository for AL Go | status not stated, demoed | [40:52](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2452s) |
| Custom job and step execution order | status not stated, demoed | [42:34](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2554s) |
| Fork alternative for AL Go customization | status not stated | [44:08](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2648s) |

## 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.

- other "deploy to custom" at [18:17](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1097s)
- other "deploy to Q&A" at [18:38](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1118s)
- other "ALOps settings" at [18:38](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1118s)
- other "pull request handler" at [19:43](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1183s)
- other "run pipeline" at [23:26](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1406s)
- other "BCBT baseline.json" at [35:35](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2135s)
- other "BC container partial script" at [39:49](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2389s)
- other "custom job/my job" at [39:12](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2352s)
- other "custom job/prepare deploy" at [40:13](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2413s)

## Quotes

- [0:19](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=19s) "AL Go for GitHub is the plug-and-play DevOps solution for Business Central development on GitHub"
- [0:59](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=59s) "You don't need any knowledge in Docker, PowerShell, or YAML, or anything like that. You don't need a dedicated DevOps engineer"
- [4:01](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=241s) "There are three types of settings in AL Go for GitHub really. There's repository wide settings"
- [7:45](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=465s) "AL Go for GitHub version 3.2"
- [8:34](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=514s) "Every time you have a CI CD or build running, there'll be a job called check for updates"
- [10:35](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=635s) "what we did in AL Go for GitHub was to add support for HSM key storage in Azure Key Vault"
- [13:25](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=805s) "the real way of of doing this going forward is to create a new setting called deploy to an environment name, meaning deploy to"
- [15:11](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=911s) "you can set it to true or false, no matter whether it's a it's a production environment or a um or a sandbox environment"
- [15:50](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=950s) "the reason for that is really another newcomer in in this version, which is custom deployment"
- [23:56](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1436s) "a new functionality that allows AL Go to build apps without containers, and allowed GitHub to cache artifacts"
- [24:07](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1447s) "GitHub hosted runner Linux runners are half the price, and uh they are 33 approximately percent faster than the Windows runners"
- [26:55](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1615s) "pulling generic image takes 4 minutes creating a container takes 7 minutes. So, 11 minutes of these 14 or 12 minutes actually goes for"
- [27:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1650s) "this build actually took 4 minutes and 42 seconds. So, it's quite a bit faster, 12 minutes faster than the other build"
- [27:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1650s) "we do not publish apps, use compiler folder, runs on Ubuntu and GitHub runner Ubuntu click actions and we'll see that this build actually"
- [29:17](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1757s) "for a free skew of of GitHub, there's like 2,000 minutes included for free of of of runners. Uh that is that equals to"
- [31:03](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1863s) "GitHub says that triggering a workflow from a workflow is not possible using the GitHub token. Uh meaning that if we run a workflow"
- [34:00](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2040s) "there's no promises, no dates. I know that it looks like everything is done, but we might still like pull the plug and say"
- [36:41](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2201s) "I think 80% of partners would not need to, like, change anything. Uh they'd be able to use AL Go for GitHub as is"
- [39:12](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2352s) "I've integrated this job into my CI/CD pipeline"
- [41:19](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2479s) "added settings will also be transferred to the repo by update AL Go system files. If you already set the settings in this file,"
- [42:46](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2566s) "if there is already a a a job with the same name in the repository that it comes from the indirect repository, it will"
- [42:58](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2578s) "if you have like new jobs that are not named the same as as as jobs that are that are from AL Go or"
- [43:55](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2635s) "you just you decide when you want to uptake new changes to that, and these changes can then be be transferred to uh to"
- [44:08](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2648s) "you could also have a fork of AL Go. Uh there are different ways of doing that and and we're not sure whether we"

## Disclaimers in the video

- [7:45](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=465s) preview: If you are running the preview version, that would the template URL would be github.com microsoft AL Go PTE at preview
- [24:30](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1470s) coming-later: At some point in time, in a future version of AL Go for GitHub, these things will be set behind the scenes
- [25:47](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=1547s) other: do not publish apps will in effect disable running tests, which is the reason why we didn't like default these things
- [34:00](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2040s) preview: there's no promises, no dates... we might still like pull the plug and say we're not going to ship this at all
- [35:01](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2101s) coming-later: it's a feature that that we might add soon
- [37:28](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2248s) subject-to-change: there actually is a PR open now, and whether we're going to merge it or or include this functionality, I don't know
- [44:08](https://www.youtube.com/watch?v=WU2fLjIQSuU&t=2648s) other: we're not sure whether we are going to select one or the other. If you're seeing this listening to this video, uh have a look at the functionality. Give us some some some feedback on whether you think this is a good idea or whether we should just go with forks

Presenters (as heard): Freddy Nielsen, Freddy.