https://stefanmaron.com/tags/git/Recent content in Git on Stefan Maron | Business Central & AL DevelopmentHugo -- gohugo.ioThu, 02 Oct 2025 00:00:00 +0000https://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/viewchangesofbasepermissionsets/Fri, 18 Aug 2023 13:57:36 +0200https://stefanmaron.com/posts/viewchangesofbasepermissionsets/How to check if one of the permissions sets from Microsoft change with an update So I got asked on LinedIn how you can keep track of changes in Microsoft’s code base for Business central. This is especially necessary when using the permission sets from Microsoft. One of my tools you can use for this is the MSDyn365BC.Code.History repository on GitHub. But since this more a resource for Developers, and checking permission sets might not always be a task a developer gets assigned, I want to make sure to explain in detail, how everyone can review the changes Microsoft does to their permission sets.https://stefanmaron.com/posts/changes-in-msdyn365bc-code-history/Fri, 07 Jan 2022 11:48:53 +0000https://stefanmaron.com/posts/changes-in-msdyn365bc-code-history/Today you may have already noticed something like this if you have a local clone of MSDyn365BC.Code.History to use with VS Code. I am going to explain what the hell is going on, and how to solve it ;) The history was rewritten I had a couple of recommendations to improve this repository. That includes a .gitignore and some changes of the settings in the workspace files. But since this repo is a bit different compared to “normal” repos, its not that easy to just merge a pull request.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/validate-a-commit-before-it-is-committed/Thu, 10 Jun 2021 14:20:29 +0000https://stefanmaron.com/posts/validate-a-commit-before-it-is-committed/Recently there was this question about how to do version numbering when working with AL Apps and automatic builds: It started a discussion about when to update which part of the version number and how that is done. The discussion will be continued today (10th June 2021 9pm CEST) on Discord if you are interested to join/listen: waldo on Twitter: “For whomever is interested - this Thursday, 9pm CEST, we’ll have a discussion on this topic (handling app versions) on the #msdyn365bc discord: https://t.https://stefanmaron.com/posts/clean-up-after-yourself-git/Wed, 10 Mar 2021 07:00:30 +0000https://stefanmaron.com/posts/clean-up-after-yourself-git/You may know this problem: After a while working with feature branches your local git repository is a mess of many branches which don’t event exist anymore on your remote. (GitHub/GitLab/DevOps) You could delete these local branches manually but if you are as lazy as I am, you might want to read on and just take my solution for this ;) I wrote a short function in PowerShell which cleans up branches for me: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.https://stefanmaron.com/posts/in-vs-code-you-want-to-stage-manually/Mon, 09 Nov 2020 15:34:55 +0000https://stefanmaron.com/posts/in-vs-code-you-want-to-stage-manually/After a longer break with blogging, I am now back with a really short one. But I thought this would be worth sharing ;) Thanks to @waldo1001 and @KarolakNatalie who opened my eyes on this one :) You might know this little message, although you might have already forgotten that you got asked, when you fist started working with VS Code. It seems like this can really save some time and work.https://stefanmaron.com/posts/automated-export-objects-from-c-al/Mon, 07 Sep 2020 05:44:17 +0000https://stefanmaron.com/posts/automated-export-objects-from-c-al/This time I have some tips on how to use GIT integration when developing in C/AL with docker. When used to AL development one of the first things to notice when going back to C/AL is, that you do not have any version control. To solve this problem, I added a little bit of SQL code to the [Object] table as SQL Trigger. This trigger exports each edited object as TXT file to specified folder.