--- id: video/kCTYPb5t5XQ type: video title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" summary: "AL-Go for GitHub productivity changes in the 2025 release wave 2: ALGO environment settings variables for deployment, a 'new warning' fail-on value for pull requests, page scripting results in the build summary, workflow input validation, settings schema in IDEs, and debug logging." tier: official language: en tags: - al-go - github - productivity - environment variables - deployment - pull requests - warnings - page scripting - workflow validation - settings schema - debug logging system: platform review: state: reviewed by: opus at: "2026-10-07T22:53:35.061Z" flags: [] generated: at: "2026-10-07T22:53:35.106Z" pipeline: 0.2.0 prompts: extract-video: 1 summarize-video: 2 input_hash: fee5bce670cc34e6c5b2f3c93d45560ea933deebe2074f05230db14c544706f4 evidence: - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=67s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 67 quote: These should be named ALGO environment settings and can be defined for each of your environments. - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=78s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 78 quote: It should be noted these are available only during deployment jobs and therefore not all of your settings should be put into this variable. - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=125s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 125 quote: The fail on setting has existed for a while, but it now accepts a new value, new warning. - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=209s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 209 quote: What this will do is it will still run the workflow partially, create a release and attack in your repository, but the workflow will - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=237s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 237 quote: For now, this is implemented only for create release and increment version, but is made in a flexible way that will allow us to - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=277s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 277 quote: You will now get also complete like shown in the screenshot which will help you discover uh settings more easily. On top of that, - kind: video url: https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=329s title: "What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)" date: "2025-10-01T00:00:00Z" commit: null t: 329 quote: What's new is that we have focused on putting extra logs that will help us debug your issues in here. links: learn: [] objects: [] features: [] topics: [] localizations: [] videos: [] posts: [] guidelines: [] video_id: kCTYPb5t5XQ channel: yt-microsoft source_name: Microsoft Dynamics 365 Business Central (YouTube) url: https://www.youtube.com/watch?v=kCTYPb5t5XQ published_at: "2025-10-01T00:00:00Z" duration_s: 362 captions: full audience: - developer - administrator - partner chapters: - t: 0 title: Introduction and overview - t: 52 title: Environment variables for deployment - t: 114 title: Block pull requests on new warnings - t: 150 title: Page scripting test visualizer - t: 175 title: Workflow input validation - t: 237 title: Settings schema and autocompletion - t: 294 title: Debug logging improvements features: - name: Environment variables for deployment status: unclear t: 52 verified: false status_source: video - name: Fail on new warnings for pull requests status: unclear t: 125 verified: false status_source: video - name: Page scripting test visualizer status: unclear t: 150 verified: false status_source: video - name: Workflow input validation status: unclear t: 187 verified: false status_source: video - name: Settings schema and autocompletion status: unclear t: 254 verified: false status_source: video - name: Debug logging enhancements status: unclear t: 294 verified: false status_source: video objects_mentioned: - other create release workflow - other increment version workflow quotes: - t: 67 text: These should be named ALGO environment settings and can be defined for each of your environments. check: exact - t: 78 text: It should be noted these are available only during deployment jobs and therefore not all of your settings should be put into this variable. check: exact - t: 125 text: The fail on setting has existed for a while, but it now accepts a new value, new warning. check: exact - t: 209 text: What this will do is it will still run the workflow partially, create a release and attack in your repository, but the workflow will check: exact - t: 237 text: For now, this is implemented only for create release and increment version, but is made in a flexible way that will allow us to check: exact - t: 277 text: You will now get also complete like shown in the screenshot which will help you discover uh settings more easily. On top of that, check: exact - t: 329 text: What's new is that we have focused on putting extra logs that will help us debug your issues in here. check: exact --- # What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2) > AL-Go for GitHub productivity changes in the 2025 release wave 2: ALGO environment settings variables for deployment, a 'new warning' fail-on value for pull requests, page scripting results in the build summary, workflow input validation, settings schema in IDEs, and debug logging. [Watch on YouTube](https://www.youtube.com/watch?v=kCTYPb5t5XQ) · Microsoft Dynamics 365 Business Central (YouTube) · 2025-10-01 · 6:02 · tier official · reviewed (checked by Opus) ## Overview The video walks through six AL-Go for GitHub improvements aimed at removing small inefficiencies in development workflows. They cover deployment configuration, pull request quality gates, test result visibility, early workflow failure, settings discovery and troubleshooting. Environment-specific settings can be moved out of the main settings file into per-environment variables used in deployment jobs. Pull requests can be blocked on newly introduced warnings. Page scripting test results appear in the build summary. Create release and increment version workflows validate inputs up front. Settings now have schema support in Visual Studio Code, and debug logging is kept separate from regular logs. The settings schema and debug logging were demoed. ## Key points - Settings can now be placed in environment variables named ALGO environment settings, defined per environment (for example the deploy to setting), to declutter the main settings file. They are available only during deployment jobs, so not all settings belong there. - The environment variables do not support the runs-on, shell and continuous deployment properties. Define those in the main settings file or in repository/organization settings. - The existing fail-on setting accepts a new value 'new warning'. It compares warnings in the pull request build to the last good CI/CD build and blocks the pull request if new warnings appear. - The new warning check does not run on the CAC job, so CAC warnings do not block CI/CD. - Page scripting test results show in the build summary like regular and performance tests. No new setting is needed, and results appear only if page scripting tests run. - Workflow input validation fails workflows early, for example on a wrong version number format in create release. It is currently implemented only for the create release and increment version workflows. - AL-Go settings have schema support in IDEs such as Visual Studio Code, with autocomplete, tool tips and links to documentation. When reporting issues, run workflows with GitHub's debug logging enabled; AL-Go adds extra debug logs there without cluttering regular logs. ## Chapters - [0:00](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=0s) Introduction and overview - [0:52](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=52s) Environment variables for deployment - [1:54](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=114s) Block pull requests on new warnings - [2:30](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=150s) Page scripting test visualizer - [2:55](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=175s) Workflow input validation - [3:57](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=237s) Settings schema and autocompletion - [4:54](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=294s) Debug logging improvements ## Features | Feature | Status | At | |---|---|---| | Environment variables for deployment | status not stated | [0:52](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=52s) | | Fail on new warnings for pull requests | status not stated | [2:05](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=125s) | | Page scripting test visualizer | status not stated | [2:30](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=150s) | | Workflow input validation | status not stated | [3:07](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=187s) | | Settings schema and autocompletion | status not stated, demoed | [4:14](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=254s) | | Debug logging enhancements | status not stated, demoed | [4:54](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=294s) | ## 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 "create release workflow" at [3:29](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=209s) - other "increment version workflow" at [3:57](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=237s) ## Quotes - [1:07](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=67s) "These should be named ALGO environment settings and can be defined for each of your environments." - [1:18](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=78s) "It should be noted these are available only during deployment jobs and therefore not all of your settings should be put into this variable." - [2:05](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=125s) "The fail on setting has existed for a while, but it now accepts a new value, new warning." - [3:29](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=209s) "What this will do is it will still run the workflow partially, create a release and attack in your repository, but the workflow will" - [3:57](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=237s) "For now, this is implemented only for create release and increment version, but is made in a flexible way that will allow us to" - [4:37](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=277s) "You will now get also complete like shown in the screenshot which will help you discover uh settings more easily. On top of that," - [5:29](https://www.youtube.com/watch?v=kCTYPb5t5XQ&t=329s) "What's new is that we have focused on putting extra logs that will help us debug your issues in here." Presenters (as heard): Sebastian.