<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI-CD on DVLUP</title><link>/en/tags/ci-cd/</link><description>Recent content in CI-CD on DVLUP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 15 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Dependabot Pull Requests</title><link>/en/blog/2026.01.15-automatic-dependabot-prs/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>/en/blog/2026.01.15-automatic-dependabot-prs/</guid><description>&lt;p&gt;Most of us are familiar with Dependabot and how it can open an Issue in your GitHub repo when there&amp;rsquo;s a pending dependency update or a security issue. However, did you know that you can also have it automatically open a Pull Request, do all the builds, make sure checks pass, and &lt;strong&gt;merge&lt;/strong&gt; it, too?&lt;/p&gt;&#10;&lt;p&gt;I find this capability very helpful and time saving when the dependencies are not core SDK components. Particualrly with node.js projects, there are can be a lot of updates that are not related directly to the code, but instead of part of the toolchain or IDE. These updates take time to manually do and can be annoying to maintain.&lt;/p&gt;</description></item><item><title>Free Yourself With DevOps</title><link>/en/blog/2022.03.04-free-yourself-with-devops/</link><pubDate>Fri, 04 Mar 2022 00:00:00 +0000</pubDate><guid>/en/blog/2022.03.04-free-yourself-with-devops/</guid><description>&lt;p&gt;As you evolve as a developer, you start to venture into the world of CI-CD. This is because you want to spend more time coding and less time with the repetitive and tiresome nature of compiling for different targets, packaging and publishing.&lt;/p&gt;&#10;&lt;p&gt;I frequently write content about CI-CD; whether it is Azure DevOps, GitHub Actions or just a PowerShell command that does a ton of work for you. In today&amp;rsquo;s post, I&amp;rsquo;m going to take you on a journey that shows you how to use Azure DevOps to automatically build, package and publish your app to the Microsoft Store.&lt;/p&gt;</description></item><item><title>Building .NET MAUI with GitHub Actions</title><link>/en/blog/2021.11.24-building-net-maui-with-github-actions/</link><pubDate>Wed, 24 Nov 2021 00:00:00 +0000</pubDate><guid>/en/blog/2021.11.24-building-net-maui-with-github-actions/</guid><description>&lt;p&gt;If you&amp;rsquo;re a fan of using GitHub Actions or Azure DevOps, you might have had some trouble configuring builds for .NET MAUI. This is likely due to needing specific workloads installed and understanding what parameters to use for a single project to compile for multiple target platforms.&lt;/p&gt;&#10;&lt;p&gt;In today&amp;rsquo;s post, I&amp;rsquo;ll show you how to setup your build that will work for any MAUI target platform. If you would like to review the final result as you read through this, here&amp;rsquo;s the workflow file =&amp;gt; &lt;a href="https://github.com/LanceMcCarthy/DevOpsExamples/blob/main/.github/workflows/main_build-maui.yml" target="_blank" rel="noopener"&gt;DevOpsExamples/main_build-maui.yml&lt;/a&gt;&#10;.&lt;/p&gt;</description></item></channel></rss>