<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github Enterprise on Nick Perkins</title>
    <link>https://nickperkins.au/tags/github-enterprise/</link>
    <description>Recent content in Github Enterprise on Nick Perkins</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 25 Jul 2025 14:30:00 +1000</lastBuildDate>
    <atom:link href="https://nickperkins.au/tags/github-enterprise/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GitHub Enterprise Reality Check: A DevOps Engineer&#39;s Perspective</title>
      <link>https://nickperkins.au/article/github-enterprise-reality-check/</link>
      <pubDate>Fri, 25 Jul 2025 14:30:00 +1000</pubDate>
      <guid>https://nickperkins.au/article/github-enterprise-reality-check/</guid>
      <description>Over the past couple of years, I&amp;rsquo;ve been working extensively with GitHub Enterprise in large organisational settings. While GitHub has built an exceptional developer experience and continues to ship features at an impressive pace, the reality is that GitHub Enterprise still has significant gaps when it comes to enterprise-scale operations. Let me share what I&amp;rsquo;ve discovered about the current state of GitHub Enterprise from a platform engineering perspective.&#xA;Photo by James Harrison on Unsplash The Repository-Centric Challenge GitHub&amp;rsquo;s architecture is fundamentally repository-focused, which works brilliantly for individual projects and small teams.</description>
    </item>
  </channel>
</rss>
