Unlocking the power of GitOps means learning to use Git as the source of truth for deployments. Key to that is understanding the three models used for defining your GitOps practices.

Packages are code, too! Like any other code solution, it’s important to be able to test your work. In this post, you’ll learn how to test a custom .NET package that adds ZIP support to the build process.

In my last post, I showed you how to use MSBuild to automatically create a ZIP package for deployment in .NET. Now, I’ll show you how to automate distributing those changes to developers using a NuGet package.

The process of compiling a .NET project and creating a ZIP file for deployment is often more complicated than it needs to be. Most CI/CD systems use a series of commands and external dependencies to build and package the project. This post shows how to use built-in functionality to simplify the process to a single call to dotnet publish.

Submodules can require some additional considerations during a migration. If the submodule repositories have large files that need to be migrated to LFS, the change to the commit IDs can break the submodules. This post explains why the problem happens, how to avoid issues during migration, and how to fix problems when they happen.