https://stefanmaron.com/tags/github-actions/Recent content in GitHub Actions on Stefan Maron | Business Central & AL DevelopmentHugo -- gohugo.ioFri, 27 Feb 2026 07:00:00 +0100https://stefanmaron.com/posts/optimizing-bc-code-history-range-requests/Fri, 27 Feb 2026 07:00:00 +0100https://stefanmaron.com/posts/optimizing-bc-code-history-range-requests/The MSDyn365BC.Sandbox.Code.History repository automatically tracks every version of the Microsoft Business Central application source code across roughly 50 countries. Two GitHub Actions workflows run daily, picking up new BC sandbox artifacts and committing the AL source to version-controlled branches. It works well — but builds had started failing silently, and once I started digging in, things unraveled fast. Fixing what was broken first The original trigger was rebase failures. When late hotfix versions created merge conflicts during git pull --rebase, the scripts relied on fragile output string matching to detect and resolve them.https://stefanmaron.com/posts/turning-streams-into-blog-posts/Tue, 24 Feb 2026 16:00:00 +0100https://stefanmaron.com/posts/turning-streams-into-blog-posts/I’ll be honest: I’m lazy when it comes to writing blog posts. Not lazy about sharing — I try to stream regularly, push code to GitHub, drop things in the community Discord. But sitting down to write a structured article about something I just spent two hours live coding? That rarely happens. The stream is the content. I jump on, explain what I’m doing, answer questions live, push something to GitHub, maybe add chapters via AI later.https://stefanmaron.com/posts/blog-post-late-hotfix-handling/Thu, 02 Oct 2025 00:00:00 +0000https://stefanmaron.com/posts/blog-post-late-hotfix-handling/You might have noticed some divergent branch errors when trying to pull from the MSDyn365BC.Sandbox.Code.History repository lately. I am going to explain what the hell is going on, and how to solve it ;) The Problem As mentioned in Issue #4 , tracking changes in the repository was becoming increasingly difficult. Microsoft occasionally releases hotfix versions with version numbers lower than already-published versions. For example: Version 27.1.40348 gets committed to the repository A few days later, Microsoft releases version 27.https://stefanmaron.com/posts/msdyn365bc-code-history-tips-tricks/Sat, 19 Oct 2024 09:00:00 +0200https://stefanmaron.com/posts/msdyn365bc-code-history-tips-tricks/If you’ve ever tried to search for something in the MsDyn365BC.Code.History repository directly on GitHub, you’ve probably noticed it stopped working. The GitHub code search just returns no results. You can watch the full stream on YouTube if you want to follow along. The fix is simple: open the repository in the browser-based VS Code instead. Just navigate to the repo and press . on your keyboard — or change github.https://stefanmaron.com/posts/msdyn365.code.history_updates/Thu, 17 Oct 2024 06:07:34 +0200https://stefanmaron.com/posts/msdyn365.code.history_updates/You might have noticed already that I made some changes to the https://github.com/StefanMaron/MSDyn365BC.Code.History repository. I want to use this blog to explain a little the what, and the why :) The what I started this with the other repository, the MSDyn365BC.Sandbox.Code.History repository. I modified my old Commit generation script a little bit so it can be used in Github Actions. With the GitHub actions, I am able to run each country seprately and in parallel, which saves a TON of time.https://stefanmaron.com/posts/lintercop-lc0068-indirect-permissions-fixes/Tue, 03 Sep 2024 09:00:00 +0100https://stefanmaron.com/posts/lintercop-lc0068-indirect-permissions-fixes/This stream happened to land on a good day — I’d just been accepted as a Microsoft MVP, so I opened with that before diving straight into bug fixes for LinterCop . The focus was on LC0068, the rule that warns when an object is missing the Permissions property for table data it touches, and there were a handful of community-reported false positives sitting in the issue tracker that needed attention.https://stefanmaron.com/posts/basic-repo-setup-with-al-go/Thu, 15 Aug 2024 09:00:00 +0100https://stefanmaron.com/posts/basic-repo-setup-with-al-go/Every new Business Central project starts with the same question: how do I get from zero to a working CI/CD pipeline without wasting a day on config? This stream walks through the entire setup — from clicking “Use this template” on GitHub all the way to running a release and deploying to an environment. The full stream is on YouTube if you want to follow along in real time. Choosing your AL-Go template I use AL-Go for all my projects.https://stefanmaron.com/posts/business-central-lintercop-with-older-versions-of-bc/Tue, 11 Jan 2022 05:37:14 +0000https://stefanmaron.com/posts/business-central-lintercop-with-older-versions-of-bc/If you want to run pipelines with the LinterCop, you can use Run-ALPipeline and pass in the path to the LinterCop.dll via the parameter - CustomCops. But when running pipelines for various versions of BusinessCentral you might encounter errors like this: Microsoft.Dynamics.Nav.CodeAnalysis, Version=8.2.8.24543, Culture=neutral, PublicKeyToken=31bf3856ad364e35'(,): warning : An instance of analyzer http://BusinessCentral.LinterCop.Design.Rule0012DoNotUseObjectIdInSystemFunctions cannot be created from C:\Agent\LinterCop\BusinessCentral.LinterCop.dll : Could not load file or assembly 'Microsoft.Dynamics.Nav.CodeAnalysis, Version=8.2.8.24543, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.https://stefanmaron.com/posts/updates-on-my-lintercop-project/Wed, 17 Nov 2021 06:20:47 +0000https://stefanmaron.com/posts/updates-on-my-lintercop-project/In the last days, I managed to get some new updates for you released. Since this would be too much for a tweet, I will summarize here what changed, what will change in the next days (hopefully 🙃 ), and what is planned for future updates. What changed lately? Pipelines and automated builds The biggest change I did in the last weeks, was to introduce pipelines and automated builds on GitHub for the LinterCop.https://stefanmaron.com/posts/msdyn365bc-code-history-got-a-few-updates/Wed, 23 Jun 2021 06:00:06 +0000https://stefanmaron.com/posts/msdyn365bc-code-history-got-a-few-updates/Over the last few month a collected a few requests to improve or change the MSDyn365BC.Code.History repository. Last weekend I finally managed to address them and since Sunday I rebuild the whole Repository. Today its finally going live: https://github.com/StefanMaron/MSDyn365BC.Code.History Include Translation files Since today, (hopefully) all translation files are included. I never did this but in case you need to, you can now compare them. For performance reasons they are excluded from search in all the workspaces that are part of the repository tho.https://stefanmaron.com/posts/msdyn365bc-code-history/Wed, 13 Jan 2021 16:28:03 +0000https://stefanmaron.com/posts/msdyn365bc-code-history/Did you ever wonder what was changed in a cumulative update in Business Central? Sure, you can read the update notes from Microsoft and read the list of bug fixes they made. But I mean like, really know what was changed. Like, which line was changed on the customer table from between 2 versions? Well, I did. For my own code I can always go to the repository and see all the code history.