<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/git/</link><description>Recent content in Git on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure DevOps Wiki to a Corporate PDF</title><link>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/from-azure-devops-wiki-to-a-corporate-pdf/</guid><description>&lt;p&gt;The project documentation is in good shape. The team has been maintaining an Azure DevOps wiki, the architecture pages link to the detailed design, and the deployment instructions sit alongside the decisions that explain them.&lt;/p&gt;
&lt;p&gt;Then comes the handover request: “Can you send us the design document as a PDF? Please use the company template.”&lt;/p&gt;
&lt;p&gt;That is a reasonable request. The recipient might not have access to Azure DevOps. An architecture board may need a fixed version to review, or the customer may need to file the document in a records system. A wiki is useful for the people doing the work; a controlled document is useful for the people accepting it.&lt;/p&gt;</description></item><item><title>Network Change Detection with Oxidized and Git</title><link>https://damianflynn.com/posts/change-detection-using-oxidized/</link><pubDate>Thu, 17 Nov 2022 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/change-detection-using-oxidized/</guid><description>&lt;p&gt;The process is very simple:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Login to each device in the router list &lt;code&gt;router.db&lt;/code&gt;,&lt;/li&gt;
&lt;li&gt;Run Commands to get the information that will be saved&lt;/li&gt;
&lt;li&gt;Clean the output&lt;/li&gt;
&lt;li&gt;Commit the Changes to GIT Repository&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The tool is coded in &lt;em&gt;Ruby&lt;/em&gt;, and implements a Domain Specific Language (DSL) for interaction.&lt;/p&gt;
&lt;p&gt;Finally, there is a Web based User experience included in the solution so we can get a fast overview of the world.&lt;/p&gt;</description></item><item><title>Building a Jekyll Site with Azure DevOps: Docker and Native Pipelines</title><link>https://damianflynn.com/posts/constructing-a-new-home-with-jekyll-and-azure-devops/</link><pubDate>Wed, 10 Oct 2018 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/constructing-a-new-home-with-jekyll-and-azure-devops/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="migrating-like-a-jekyll-using-azure-devops"&gt;&lt;a href="#migrating-like-a-jekyll-using-azure-devops" class="header-mark" aria-label="Header mark for 'Migrating like a Jekyll using Azure DevOps'"&gt;&lt;/a&gt;
 &lt;div id="migrating-like-a-jekyll-using-azure-devops" class="absolute -top-28"&gt;&lt;/div&gt;
 Migrating like a Jekyll using Azure DevOps
&lt;/h1&gt;
&lt;p&gt;One of the unspoken truths behind the lack of posts on ths blog in recent history was due to a few bugs, which in the end resulted in an experience where from home it appeared that any new content was published and working; but outside this fortress in the real world, there was a large silence echoing.&lt;/p&gt;</description></item></channel></rss>