---
id: video/HYqjpyHZ84Q
type: video
title: AL-Go for Github March Office Hour
summary: "AL-Go for GitHub March office hour covering the 6.4 release and version 7 plans: incremental builds, NuGet feed select mode, multi-branch system file updates, publishing from pull requests, code signing options, and Q&A on migrating from Azure DevOps."
tier: official
language: en
tags:
  - al-go
  - github
  - ci-cd
  - nuget-feeds
  - incremental-builds
  - pull-requests
  - dependency-resolution
  - containers
  - versioning
  - multi-branch-updates
  - azure-devops
  - code-signing
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-07T22:57:17.465Z"
  flags: []
generated:
  at: "2026-10-07T22:57:17.530Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: 109350f65357a29aa37a634f89831afd570d9c5e627f9977785d17f5a3791d9a
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s
    title: "BC container settings from variables: preview"
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 163
    quote: So those things are in preview right now and will also be included in version seven of Elgo for GitHub.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s
    title: "Publish apps from pull requests: preview"
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 163
    quote: So those things are in preview right now and will also be included in version seven of Elgo for GitHub.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=854s
    title: "Incremental builds: generally available"
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 854
    quote: so I'm expecting that uh this is the feature that we we just released in version 6.4 which is incremental builds.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=77s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 77
    quote: by the way, we also just recorded the launch event video, so in a few days you will be able to see what's new
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=93s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 93
    quote: right now we we just launched um version 6.4 a week ago.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 163
    quote: So those things are in preview right now and will also be included in version seven of Elgo for GitHub.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=225s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 225
    quote: You can also run it on a schedule which is highly recommended. So you can you can set up this workflow schedule and say
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=268s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 268
    quote: The difference between earliest and earliest matching is that the earliest matching is also taking dependencies into consideration.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=717s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 717
    quote: We do not have resources to to create algo for GitHub to or ago for Azure DevOps. Um so algo go for GitHub is
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=801s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 801
    quote: What we hope is that more and more partners will start um publishing their appsource apps as runtime packages and sharing those with partners
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=854s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 854
    quote: I'm expecting that uh this is the feature that we we just released in version 6.4 which is incremental builds
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=880s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 880
    quote: whenever you you push some modifications to the repo, it will only build the apps that you actually modified in that uh push
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=892s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 892
    quote: it will also then only deploy that app uh to your environment when it deploys. It'll it'll find the last known good built and
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=990s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 990
    quote: probably you'll find that the majority of things that you're already doing is is somehow available in in algo for GitHub as well. Um
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1283s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1283
    quote: the ability to uninstall or unpublish actually an an old app um was not available. That is available now
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1302s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1302
    quote: So, we should look into getting that uh added to the publish to environment so that it it automatically unpublishes the old app
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1389s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1389
    quote: Well, it's it's currently not possible. I have thought about adding like a setting to allow you to point to a different variable
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1572s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1572
    quote: when you have a an incremental build, then it will actually copy the artifacts from the last known good build
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1617s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1617
    quote: we right now we are selecting a full build whenever you make any changes to settings
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1629s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1629
    quote: and update Elgo system files for example will will cause a full build afterwards uh which is probably too much
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1732s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 1732
    quote: If you set up the builds on a schedule, um you can specify that on schedule that you'll run incremental builds on a schedule
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2000s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2000
    quote: right now what you set up is is is a chron tab and I guess that can be used for a specific time
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2149s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2149
    quote: you can you can build those uh in three different modes one default one for next major and one for next minor
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2558s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2558
    quote: typically people will not be able to get a certificate and a password anymore, but I expect that you still have a pfx file
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2634s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2634
    quote: The new mechanism to sign the apps is either using trusted signing on Azure or using um uh Azure key to um to host
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2742s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2742
    quote: we've switched all our signing to to trusted signing instead. So um which is something you need to do probably within the next I
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2982s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 2982
    quote: Before we used the create release action and it worked out of the box. Now something has changed few weeks ago and we have
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3113s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 3113
    quote: we've been contemplating using the Q&A section in the descript discussions but haven't really done anything
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3167s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 3167
    quote: And maybe we should remove the the question template from the issues and point to discussions instead.
  - kind: video
    url: https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3167s
    title: AL-Go for Github March Office Hour
    date: "2025-05-01T16:08:21.000Z"
    commit: null
    t: 3167
    quote: I know that I have haven't been as active on answering discussions as I have on issues that might be a reason for for
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: HYqjpyHZ84Q
channel: yt-microsoft
source_name: Microsoft Dynamics 365 Business Central (YouTube)
url: https://www.youtube.com/watch?v=HYqjpyHZ84Q
published_at: "2025-05-01T16:08:21.000Z"
duration_s: 3254
captions: full
audience:
  - developer
  - administrator
  - partner
chapters:
  - t: 0
    title: Welcome and introduction to AL-Go office hours
  - t: 77
    title: Overview of AL-Go version 6.4 and 7 releases
  - t: 119
    title: Update AL-Go system files on multiple branches
  - t: 225
    title: NuGet feed select mode and BC container settings
  - t: 306
    title: Publish apps from pull requests
  - t: 417
    title: Q&A - Publishing from PR to containers
  - t: 578
    title: Q&A - Dependency resolution and NuGet packages
  - t: 705
    title: Q&A - Azure DevOps and AppSource dependencies
  - t: 816
    title: Incremental builds and artifact handling
  - t: 919
    title: Migration from Azure DevOps to AL-Go
  - t: 1068
    title: Dependency resolution issues and GitHub NuGet
  - t: 1139
    title: GitHub repository links and resources
  - t: 1263
    title: Auto-uninstall capability for old apps
  - t: 1373
    title: Multiple organizational variables support
  - t: 1451
    title: Azure DevOps and GitHub integration
  - t: 1572
    title: Incremental builds and code change detection
  - t: 1680
    title: Scheduled vs manual incremental builds
  - t: 1761
    title: Code analyzer warnings and error handling
  - t: 1913
    title: Scheduled deployments and workflow timing
  - t: 2107
    title: Build modes for testing multiple versions
  - t: 2189
    title: Q&A and field length warnings
  - t: 2343
    title: Field length changes and SQL considerations
  - t: 2528
    title: Code signing mechanisms and certificate handling
  - t: 2773
    title: Secret configuration for code signing
  - t: 2869
    title: Create release action workflow issue
  - t: 3009
    title: GitHub discussions and community engagement
features:
  - name: Update AL-Go system files on multiple branches
    status: unclear
    t: 180
    verified: false
    status_source: video
  - name: NuGet feed select mode
    status: unclear
    t: 246
    verified: false
    status_source: video
  - name: BC container settings from variables
    status: preview
    t: 306
    verified: true
    status_source: video
  - name: Publish apps from pull requests
    status: preview
    t: 342
    verified: true
    status_source: video
  - name: GitHub Packages for internal dependencies
    status: unclear
    t: 601
    verified: false
    status_source: video
  - name: Incremental builds
    status: ga
    t: 854
    verified: true
    status_source: video
  - name: Runtime packages for AppSource apps
    status: unclear
    t: 801
    verified: false
    status_source: video
  - name: AL-Go workshop for migration
    status: unclear
    t: 919
    verified: false
    status_source: video
  - name: AL-Go settings reference
    status: unclear
    t: 1005
    verified: false
    status_source: video
  - name: Auto-uninstall old app versions
    status: unclear
    t: 1263
    verified: false
    status_source: video
  - name: Multiple organizational variables
    status: unclear
    t: 1373
    verified: false
    status_source: video
  - name: Azure Boards GitHub integration
    status: unclear
    t: 1451
    verified: false
    status_source: video
  - name: Smart rebuild on settings changes
    status: unclear
    t: 1617
    verified: false
    status_source: video
  - name: Scheduled incremental builds
    status: unclear
    t: 1722
    verified: false
    status_source: video
  - name: Treat warnings as errors setting
    status: unclear
    t: 1839
    verified: false
    status_source: video
  - name: Fail on warnings workflow setting
    status: unclear
    t: 1898
    verified: false
    status_source: video
  - name: Scheduled deployment to environment
    status: unclear
    t: 1974
    verified: false
    status_source: video
  - name: Build modes for version testing
    status: unclear
    t: 2123
    verified: false
    status_source: video
  - name: Trusted signing with Azure
    status: unclear
    t: 2634
    verified: false
    status_source: video
  - name: Code signing via Azure Key Vault and net sign
    status: unclear
    t: 2634
    verified: false
    status_source: video
  - name: Create release action
    status: unclear
    t: 2982
    verified: false
    status_source: video
  - name: GitHub discussions for community Q&A
    status: unclear
    t: 3093
    verified: false
    status_source: video
objects_mentioned:
  - other Business Central
  - other code sign certificate URL
  - other code sign certificate password
  - other create release action
quotes:
  - t: 77
    text: by the way, we also just recorded the launch event video, so in a few days you will be able to see what's new
    check: exact
  - t: 93
    text: right now we we just launched um version 6.4 a week ago.
    check: exact
  - t: 163
    text: So those things are in preview right now and will also be included in version seven of Elgo for GitHub.
    check: exact
  - t: 225
    text: You can also run it on a schedule which is highly recommended. So you can you can set up this workflow schedule and say
    check: exact
  - t: 268
    text: The difference between earliest and earliest matching is that the earliest matching is also taking dependencies into consideration.
    check: exact
  - t: 717
    text: We do not have resources to to create algo for GitHub to or ago for Azure DevOps. Um so algo go for GitHub is
    check: exact
  - t: 801
    text: What we hope is that more and more partners will start um publishing their appsource apps as runtime packages and sharing those with partners
    check: exact
  - t: 854
    text: I'm expecting that uh this is the feature that we we just released in version 6.4 which is incremental builds
    check: exact
  - t: 880
    text: whenever you you push some modifications to the repo, it will only build the apps that you actually modified in that uh push
    check: exact
  - t: 892
    text: it will also then only deploy that app uh to your environment when it deploys. It'll it'll find the last known good built and
    check: exact
  - t: 990
    text: probably you'll find that the majority of things that you're already doing is is somehow available in in algo for GitHub as well. Um
    check: exact
  - t: 1283
    text: the ability to uninstall or unpublish actually an an old app um was not available. That is available now
    check: exact
  - t: 1302
    text: So, we should look into getting that uh added to the publish to environment so that it it automatically unpublishes the old app
    check: exact
  - t: 1389
    text: Well, it's it's currently not possible. I have thought about adding like a setting to allow you to point to a different variable
    check: exact
  - t: 1572
    text: when you have a an incremental build, then it will actually copy the artifacts from the last known good build
    check: exact
  - t: 1617
    text: we right now we are selecting a full build whenever you make any changes to settings
    check: exact
  - t: 1629
    text: and update Elgo system files for example will will cause a full build afterwards uh which is probably too much
    check: exact
  - t: 1732
    text: If you set up the builds on a schedule, um you can specify that on schedule that you'll run incremental builds on a schedule
    check: exact
  - t: 2000
    text: right now what you set up is is is a chron tab and I guess that can be used for a specific time
    check: exact
  - t: 2149
    text: you can you can build those uh in three different modes one default one for next major and one for next minor
    check: exact
  - t: 2558
    text: typically people will not be able to get a certificate and a password anymore, but I expect that you still have a pfx file
    check: exact
  - t: 2634
    text: The new mechanism to sign the apps is either using trusted signing on Azure or using um uh Azure key to um to host
    check: exact
  - t: 2742
    text: we've switched all our signing to to trusted signing instead. So um which is something you need to do probably within the next I
    check: exact
  - t: 2982
    text: Before we used the create release action and it worked out of the box. Now something has changed few weeks ago and we have
    check: exact
  - t: 3113
    text: we've been contemplating using the Q&A section in the descript discussions but haven't really done anything
    check: exact
  - t: 3167
    text: And maybe we should remove the the question template from the issues and point to discussions instead.
    check: exact
  - t: 3167
    text: I know that I have haven't been as active on answering discussions as I have on issues that might be a reason for for
    check: snapped
---

# AL-Go for Github March Office Hour

> AL-Go for GitHub March office hour covering the 6.4 release and version 7 plans: incremental builds, NuGet feed select mode, multi-branch system file updates, publishing from pull requests, code signing options, and Q&A on migrating from Azure DevOps.

[Watch on YouTube](https://www.youtube.com/watch?v=HYqjpyHZ84Q) · Microsoft Dynamics 365 Business Central (YouTube) · 2025-05-01 · 54:14 · tier official · reviewed (checked by Opus)

## Overview

This AL-Go for GitHub office hour, published 2025-05-01, walks through what shipped in version 6.4 a week before recording and what is coming in version 7. Topics include running update AL-Go system files on multiple branches, a new NuGet feed select mode, reading BC container settings from variables, and publishing apps from pull requests to an environment for manual testing.

The second half is Q&A. It covers dependency resolution with GitHub Packages, migrating from Azure DevOps with the AL-Go workshop, how incremental builds behave on push versus scheduled and manual runs, treating warnings as errors, scheduled deployments, build modes for next major and next minor, and code signing with Azure trusted signing or Azure Key Vault. It ends with an open issue on the create release action and a discussion about using GitHub Discussions for community questions.

## Key points

- Incremental builds (released in 6.4) build and deploy only apps modified in a push and copy artifacts from the last known good build. Any settings file change currently triggers a full build, including update AL-Go system files. Changes to settings variables do not.
- Incremental builds apply to push and scheduled builds. A manual run of the CI/CD workflow does a full build.
- NuGet feed select mode has four options: earliest matching, earliest exact, latest, latest matching. Earliest matching also takes dependencies into account. It was previously hardcoded to latest matching.
- Reading BC container settings from settings variables and publishing from a pull request (PR_[number] in the publish to environment workflow) are described as in preview. PR artifacts expire after one day by default.
- Update AL-Go system files can run on multiple branches with a template URL. Running it on a schedule is recommended.
- For signing, the PFX certificate mechanism still works if secrets are configured. The newer options are Azure trusted signing or Azure Key Vault with net sign.
- Multiple organizational variables, for example separate settings for internal and PTE apps, are not currently possible. Auto-uninstall of old app versions is not yet implemented in AL-Go publish to environment.

## Chapters

- [0:00](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=0s) Welcome and introduction to AL-Go office hours
- [1:17](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=77s) Overview of AL-Go version 6.4 and 7 releases
- [1:59](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=119s) Update AL-Go system files on multiple branches
- [3:45](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=225s) NuGet feed select mode and BC container settings
- [5:06](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=306s) Publish apps from pull requests
- [6:57](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=417s) Q&A - Publishing from PR to containers
- [9:38](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=578s) Q&A - Dependency resolution and NuGet packages
- [11:45](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=705s) Q&A - Azure DevOps and AppSource dependencies
- [13:36](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=816s) Incremental builds and artifact handling
- [15:19](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=919s) Migration from Azure DevOps to AL-Go
- [17:48](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1068s) Dependency resolution issues and GitHub NuGet
- [18:59](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1139s) GitHub repository links and resources
- [21:03](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1263s) Auto-uninstall capability for old apps
- [22:53](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1373s) Multiple organizational variables support
- [24:11](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1451s) Azure DevOps and GitHub integration
- [26:12](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1572s) Incremental builds and code change detection
- [28:00](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1680s) Scheduled vs manual incremental builds
- [29:21](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1761s) Code analyzer warnings and error handling
- [31:53](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1913s) Scheduled deployments and workflow timing
- [35:07](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2107s) Build modes for testing multiple versions
- [36:29](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2189s) Q&A and field length warnings
- [39:03](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2343s) Field length changes and SQL considerations
- [42:08](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2528s) Code signing mechanisms and certificate handling
- [46:13](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2773s) Secret configuration for code signing
- [47:49](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2869s) Create release action workflow issue
- [50:09](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3009s) GitHub discussions and community engagement

## Features

| Feature | Status | At | Evidence |
|---|---|---|---|
| Update AL-Go system files on multiple branches | status not stated | [3:00](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=180s) |  |
| NuGet feed select mode | status not stated | [4:06](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=246s) |  |
| BC container settings from variables | preview | [5:06](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=306s) | "So those things are in preview right now and will also be included in version seven of Elgo for GitHub." ([2:43](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s)) |
| Publish apps from pull requests | preview | [5:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=342s) | "So those things are in preview right now and will also be included in version seven of Elgo for GitHub." ([2:43](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s)) |
| GitHub Packages for internal dependencies | status not stated | [10:01](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=601s) |  |
| Incremental builds | generally available, demoed | [14:14](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=854s) | "so I'm expecting that uh this is the feature that we we just released in version 6.4 which is incremental builds." ([14:14](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=854s)) |
| Runtime packages for AppSource apps | status not stated | [13:21](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=801s) |  |
| AL-Go workshop for migration | status not stated | [15:19](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=919s) |  |
| AL-Go settings reference | status not stated | [16:45](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1005s) |  |
| Auto-uninstall old app versions | status not stated | [21:03](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1263s) |  |
| Multiple organizational variables | status not stated | [22:53](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1373s) |  |
| Azure Boards GitHub integration | status not stated | [24:11](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1451s) |  |
| Smart rebuild on settings changes | status not stated | [26:57](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1617s) |  |
| Scheduled incremental builds | status not stated | [28:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1722s) |  |
| Treat warnings as errors setting | status not stated | [30:39](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1839s) |  |
| Fail on warnings workflow setting | status not stated | [31:38](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1898s) |  |
| Scheduled deployment to environment | status not stated | [32:54](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1974s) |  |
| Build modes for version testing | status not stated | [35:23](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2123s) |  |
| Trusted signing with Azure | status not stated | [43:54](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2634s) |  |
| Code signing via Azure Key Vault and net sign | status not stated | [43:54](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2634s) |  |
| Create release action | status not stated | [49:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2982s) |  |
| GitHub discussions for community Q&A | status not stated | [51:33](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3093s) |  |

## 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 "Business Central" at [21:03](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1263s)
- other "code sign certificate URL" at [42:29](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2549s)
- other "code sign certificate password" at [42:29](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2549s)
- other "create release action" at [49:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2982s)

## Quotes

- [1:17](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=77s) "by the way, we also just recorded the launch event video, so in a few days you will be able to see what's new"
- [1:33](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=93s) "right now we we just launched um version 6.4 a week ago."
- [2:43](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=163s) "So those things are in preview right now and will also be included in version seven of Elgo for GitHub."
- [3:45](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=225s) "You can also run it on a schedule which is highly recommended. So you can you can set up this workflow schedule and say"
- [4:28](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=268s) "The difference between earliest and earliest matching is that the earliest matching is also taking dependencies into consideration."
- [11:57](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=717s) "We do not have resources to to create algo for GitHub to or ago for Azure DevOps. Um so algo go for GitHub is"
- [13:21](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=801s) "What we hope is that more and more partners will start um publishing their appsource apps as runtime packages and sharing those with partners"
- [14:14](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=854s) "I'm expecting that uh this is the feature that we we just released in version 6.4 which is incremental builds"
- [14:40](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=880s) "whenever you you push some modifications to the repo, it will only build the apps that you actually modified in that uh push"
- [14:52](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=892s) "it will also then only deploy that app uh to your environment when it deploys. It'll it'll find the last known good built and"
- [16:30](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=990s) "probably you'll find that the majority of things that you're already doing is is somehow available in in algo for GitHub as well. Um"
- [21:23](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1283s) "the ability to uninstall or unpublish actually an an old app um was not available. That is available now"
- [21:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1302s) "So, we should look into getting that uh added to the publish to environment so that it it automatically unpublishes the old app"
- [23:09](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1389s) "Well, it's it's currently not possible. I have thought about adding like a setting to allow you to point to a different variable"
- [26:12](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1572s) "when you have a an incremental build, then it will actually copy the artifacts from the last known good build"
- [26:57](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1617s) "we right now we are selecting a full build whenever you make any changes to settings"
- [27:09](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1629s) "and update Elgo system files for example will will cause a full build afterwards uh which is probably too much"
- [28:52](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1732s) "If you set up the builds on a schedule, um you can specify that on schedule that you'll run incremental builds on a schedule"
- [33:20](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2000s) "right now what you set up is is is a chron tab and I guess that can be used for a specific time"
- [35:49](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2149s) "you can you can build those uh in three different modes one default one for next major and one for next minor"
- [42:38](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2558s) "typically people will not be able to get a certificate and a password anymore, but I expect that you still have a pfx file"
- [43:54](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2634s) "The new mechanism to sign the apps is either using trusted signing on Azure or using um uh Azure key to um to host"
- [45:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2742s) "we've switched all our signing to to trusted signing instead. So um which is something you need to do probably within the next I"
- [49:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2982s) "Before we used the create release action and it worked out of the box. Now something has changed few weeks ago and we have"
- [51:53](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3113s) "we've been contemplating using the Q&A section in the descript discussions but haven't really done anything"
- [52:47](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3167s) "And maybe we should remove the the question template from the issues and point to discussions instead."
- [52:47](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3167s) "I know that I have haven't been as active on answering discussions as I have on issues that might be a reason for for"

## Disclaimers in the video

- [1:59](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=119s) coming-later: will also be included in version seven of Elgo for GitHub
- [2:24](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=144s) preview: the ability to to to set BC container settings uh from settings variables and publish to environment from a pull request. So those things are in preview right now
- [13:36](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=816s) coming-later: we are missing a few features uh for that and and that is on our schedule to finalize the new get uh features in in the upcoming release meaning over the next half year
- [17:19](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1039s) coming-later: We know that we still need to generate more documentation and I have promised to get started on that
- [21:42](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1302s) coming-later: we should look into getting that uh added to the publish to environment so that it it automatically unpublishes the old app
- [27:22](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=1642s) subject-to-change: we might make a change to actually only do a full build on config changes or settings changes if some of these settings changes actually have any impact on the apps generated
- [34:20](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2060s) not-in-this-release: you want to be able to control it a little bit uh further and that would be something we had to yeah take as an as an idea if you can again create a GitHub issue with this one and and we can put into our backlog
- [35:35](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2135s) not-in-this-release: it is not something we will chain um automatically. It's something I mean the deployment to prod is is I guess something
- [44:18](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=2658s) other: in 2023 you were not able to get pfx files anymore
- [51:53](https://www.youtube.com/watch?v=HYqjpyHZ84Q&t=3113s) other: we've been contemplating using the Q&A section in the descript discussions but haven't really done anything

Presenters (as heard): Alexander, Ray, Christian, Tom, Oliver, Cataline Maria, Maria, Sebastian, Dominique, Tony, Unknown (primary speaker).