What's New in AL-Go for GitHub: Productivity Enhancements (2025 release wave 2)

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.

Features

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
• other “increment version workflow” at 3:57

Quotes

• 1:07 “These should be named ALGO environment settings and can be defined for each of your environments.”
• 1:18 “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 “The fail on setting has existed for a while, but it now accepts a new value, new warning.”
• 3:29 “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 “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 “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 “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.