Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://github.blog/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>The GitHub Blog</title>
  12. <atom:link href="https://github.blog/feed/" rel="self" type="application/rss+xml" />
  13. <link>https://github.blog/</link>
  14. <description>Updates, ideas, and inspiration from GitHub to help developers build and design software.</description>
  15. <lastBuildDate>Thu, 23 Oct 2025 20:53:49 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.8.3</generator>
  22.  
  23. <image>
  24. <url>https://github.blog/wp-content/uploads/2019/01/cropped-github-favicon-512.png?fit=32%2C32</url>
  25. <title>The GitHub Blog</title>
  26. <link>https://github.blog/</link>
  27. <width>32</width>
  28. <height>32</height>
  29. </image>
  30. <site xmlns="com-wordpress:feed-additions:1">153214340</site> <item>
  31. <title>How to find, install, and manage MCP servers with the GitHub MCP Registry</title>
  32. <link>https://github.blog/ai-and-ml/generative-ai/how-to-find-install-and-manage-mcp-servers-with-the-github-mcp-registry/</link>
  34. <dc:creator><![CDATA[Andrea Griffiths]]></dc:creator>
  35. <pubDate>Fri, 24 Oct 2025 16:00:00 +0000</pubDate>
  36. <category><![CDATA[AI & ML]]></category>
  37. <category><![CDATA[Generative AI]]></category>
  38. <category><![CDATA[MCP]]></category>
  39. <guid isPermaLink="false">https://github.blog/?p=91673</guid>
  40.  
  41. <description><![CDATA[<p>Learn how to bring structure and security to your AI ecosystem with the GitHub MCP Registry, the single source of truth for managing and governing MCP servers.</p>
  42. <p>The post <a href="https://github.blog/ai-and-ml/generative-ai/how-to-find-install-and-manage-mcp-servers-with-the-github-mcp-registry/">How to find, install, and manage MCP servers with the GitHub MCP Registry</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  43. ]]></description>
  44. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  45. <html><body><p>Picture this: you walk into a grocery store and nothing makes sense. The cereal is scattered across three aisles. The milk is hiding in some random cooler near self-checkout. And those produce labels? They haven&rsquo;t been updated in months.</p>
  46.  
  47.  
  48.  
  49. <p>That&rsquo;s exactly what discovering Model Context Protocol (MCP) servers felt like. Until now.</p>
  50.  
  51.  
  52.  
  53. <p>As a refresher, <a href="https://github.blog/ai-and-ml/llms/what-the-heck-is-mcp-and-why-is-everyone-talking-about-it/">MCP is how developers connect tools, APIs, and workflows to their AI systems</a>. Each MCP server is like an ingredient in your AI stack, whether it&rsquo;s Playwright for browser automation, Notion for knowledge access, or GitHub&rsquo;s own MCP server with over a hundred tools.&nbsp;</p>
  54.  
  55.  
  56.  
  57. <p>The new <a href="https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/">GitHub MCP Registry</a> changes everything by giving you a single, canonical source for discovering, installing, and managing MCP servers right on GitHub.</p>
  58.  
  59.  
  60.  
  61. <p>Here&rsquo;s what you need to know about finding the right tools for your AI stack, publishing your own servers, and setting up governance for your team.</p>
  62.  
  63.  
  64.  
  65. <p>In this blog, we&rsquo;ll walk through how to:</p>
  66.  
  67.  
  68.  
  69. <ul class="wp-block-list">
  70. <li>Install an MCP server</li>
  71.  
  72.  
  73.  
  74. <li>Publish your own</li>
  75.  
  76.  
  77.  
  78. <li>Enable governance and team use</li>
  79. </ul>
  80.  
  81.  
  82.  
  83. <p>We&rsquo;ll also share a few tips and tricks for power users. Let&rsquo;s go!</p>
  84.  
  85.  
  86.  
  87. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
  88. <iframe title="A deep dive into the GitHub MCP registry | GitHub Checkout" width="500" height="281" src="https://www.youtube.com/embed/wm1yjcTk50w?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
  89. </div></figure>
  90.  
  91.  
  92.  
  93. <h2 class="wp-block-heading" id="h-what-s-in-the-registry-today">What&rsquo;s in the registry today</h2>
  94.  
  95.  
  96.  
  97. <p>Currently, the <a href="https://github.com/mcp">GitHub MCP Registry</a> has <strong>44 MCP servers</strong>, including:</p>
  98.  
  99.  
  100.  
  101. <ul class="wp-block-list">
  102. <li><strong>Playwright</strong>: Automate and test web apps.</li>
  103.  
  104.  
  105.  
  106. <li><strong>GitHub MCP server</strong>: Access 100+ GitHub API tools.</li>
  107.  
  108.  
  109.  
  110. <li><strong>Context7</strong>, <strong>MarkItDown</strong> (Microsoft), <strong>Terraform</strong> (HashiCorp).</li>
  111.  
  112.  
  113.  
  114. <li>Partner servers from <strong>Notion, Unity, Firecrawl, Stripe,</strong> and more.</li>
  115. </ul>
  116.  
  117.  
  118.  
  119. <p>You can browse by tags, popularity, or GitHub stars to find the tools you need.</p>
  120.  
  121.  
  122.  
  123. <h2 class="wp-block-heading" id="h-how-to-install-an-mcp-server">How to install an MCP server</h2>
  124.  
  125.  
  126.  
  127. <p>The registry makes installation a one-click experience in <strong>VS Code</strong> or <strong>VS Code Insiders</strong>.</p>
  128.  
  129.  
  130.  
  131. <h3 class="wp-block-heading" id="h-example-installing-playwright">Example: Installing Playwright</h3>
  132.  
  133.  
  134.  
  135. <ol class="wp-block-list">
  136. <li>Navigate to Playwright MCP server in the GitHub MCP Registry.</li>
  137.  
  138.  
  139.  
  140. <li>Click <strong>Install in VS Code</strong>.</li>
  141.  
  142.  
  143.  
  144. <li>VS Code launches with a pre-filled configuration.</li>
  145.  
  146.  
  147.  
  148. <li>Accept or adjust optional parameters (like storage paths).</li>
  149. </ol>
  150.  
  151.  
  152.  
  153. <p>That&rsquo;s it. You&rsquo;re ready to use Playwright in your agentic workflows.</p>
  154.  
  155.  
  156.  
  157. <p>&#9989; <strong>Pro tip:</strong> Remote MCP servers (like GitHub&rsquo;s) use OAuth during install so you don&rsquo;t need to manually handle tokens or secrets. Just authenticate once and start building.</p>
  158.  
  159.  
  160.  
  161. <h2 class="wp-block-heading" id="h-how-to-publish-your-own-mcp-server">How to publish your own MCP server</h2>
  162.  
  163.  
  164.  
  165. <h3 class="wp-block-heading" id="h-1-install-the-mcp-publisher-cli">1. Install the MCP Publisher CLI</h3>
  166.  
  167.  
  168.  
  169. <ul class="wp-block-list">
  170. <li>macOS/Linux/WSL (Homebrew, recommended):</li>
  171. </ul>
  172.  
  173.  
  174.  
  175. <pre class="wp-block-code"><code>brew install mcp-publisher</code></pre>
  176.  
  177.  
  178.  
  179. <ul class="wp-block-list">
  180. <li>macOS/Linux/WSL (prebuilt binary, latest version):</li>
  181. </ul>
  182.  
  183.  
  184.  
  185. <pre class="wp-block-code"><code>"https://github.com/modelcontextprotocol/registry/releases/download/latest/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher &amp;&amp; sudo mv mcp-publisher /usr/local/bin/</code></pre>
  186.  
  187.  
  188.  
  189. <h3 class="wp-block-heading" id="h-2-initialize-your-server-json-file">2. Initialize your <code>server.json</code> file</h3>
  190.  
  191.  
  192.  
  193. <p>Navigate to your server&rsquo;s source directory and run:</p>
  194.  
  195.  
  196.  
  197. <pre class="wp-block-code"><code>cd /path/to/your/mcp-server
  198. mcp-publisher init</code></pre>
  199.  
  200.  
  201.  
  202. <p>This creates a <code>server.json</code> file. Example:</p>
  203.  
  204.  
  205.  
  206. <pre class="wp-block-code"><code>{
  207.  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  208.  "name": "io.github.yourname/your-server",
  209.  "title": "Describe Your Server",
  210.  "description": "A description of your MCP server",
  211.  "version": "1.0.0",
  212.  "packages": [
  213.    {
  214.      "registryType": "npm",
  215.      "identifier": "your-package-name",
  216.      "version": "1.0.0",
  217.      "transport": { "type": "stdio" }
  218.    }
  219.  ]
  220. }</code></pre>
  221.  
  222.  
  223.  
  224. <h3 class="wp-block-heading" id="3-prove-you-own-the-package">3. Prove you own the package</h3>
  225.  
  226.  
  227.  
  228. <p>Add the required metadata for your package type.</p>
  229.  
  230.  
  231.  
  232. <ul class="wp-block-list">
  233. <li><strong>NPM:</strong> Add an <code>"mcpName"</code> field to your <code>package.json</code>:</li>
  234. </ul>
  235.  
  236.  
  237.  
  238. <pre class="wp-block-code language-plaintext"><code>{
  239.  "name": "your-npm-package",
  240.  "mcpName": "io.github.username/server-name"
  241. }</code></pre>
  242.  
  243.  
  244.  
  245. <ul class="wp-block-list">
  246. <li><strong>PyPI/NuGet:</strong> Add this to your README:</li>
  247. </ul>
  248.  
  249.  
  250.  
  251. <pre class="wp-block-code language-plaintext"><code>mcp-name: io.github.username/server-name</code></pre>
  252.  
  253.  
  254.  
  255. <ul class="wp-block-list">
  256. <li><strong>Docker:</strong> Add a label to your Dockerfile:</li>
  257. </ul>
  258.  
  259.  
  260.  
  261. <pre class="wp-block-code language-plaintext"><code>LABEL io.modelcontextprotocol.server.name="io.github.username/server-name"</code></pre>
  262.  
  263.  
  264.  
  265. <h3 class="wp-block-heading" id="4-authentication">4. Authentication</h3>
  266.  
  267.  
  268.  
  269. <ul class="wp-block-list">
  270. <li>For GitHub-based namespaces (<code>io.github.*</code>), run:</li>
  271. </ul>
  272.  
  273.  
  274.  
  275. <pre class="wp-block-code"><code>mcp-publisher login github</code></pre>
  276.  
  277.  
  278.  
  279. <p>       This will open a browser for OAuth login.</p>
  280.  
  281.  
  282.  
  283. <ul class="wp-block-list">
  284. <li>For custom domains (<code>com.yourcompany/*</code>), follow DNS verification steps in the <a href="https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/publish-server.md">official docs</a>.</li>
  285. </ul>
  286.  
  287.  
  288.  
  289. <h3 class="wp-block-heading" id="5-publish-your-server">5. Publish your server</h3>
  290.  
  291.  
  292.  
  293. <p>Once authenticated, publish to the registry:</p>
  294.  
  295.  
  296.  
  297. <pre class="wp-block-code"><code>mcp-publisher publish</code></pre>
  298.  
  299.  
  300.  
  301. <p>If successful, your server will be discoverable in the MCP registry. You can verify with:</p>
  302.  
  303.  
  304.  
  305. <pre class="wp-block-code"><code>curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.yourname/your-server"</code></pre>
  306.  
  307.  
  308.  
  309. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  310. <p>Once you&rsquo;ve completed the steps above, email&nbsp;<a target="_blank" href="mailto:partnerships@github.com" rel="noreferrer noopener">partnerships@github.com</a>&nbsp;and request for your server to be included.</p>
  311. </blockquote>
  312.  
  313.  
  314.  
  315. <p>&#9989; <strong>Pro tips:</strong>&nbsp;</p>
  316.  
  317.  
  318.  
  319. <ul class="wp-block-list">
  320. <li><strong>Namespace:</strong> Use <code>io.github.username/*</code> for GitHub auth, or <code>com.yourcompany/*</code> for DNS-based verification.</li>
  321.  
  322.  
  323.  
  324. <li><strong>Remote endpoints:</strong> Add a <code>"remotes"</code> array in your <code>server.json</code> for cloud/HTTP endpoints:</li>
  325. </ul>
  326.  
  327.  
  328.  
  329. <pre class="wp-block-code"><code>"remotes": [
  330.  {
  331.    "type": "streamable-http",
  332.    "url": "https://yourdomain.com/yourserver"
  333.  }
  334. ]</code></pre>
  335.  
  336.  
  337.  
  338. <ul class="wp-block-list">
  339. <li><strong>Multiple deployment options:</strong> You can list both <code>"packages"</code> and <code>"remotes"</code> for hybrid deployments.</li>
  340.  
  341.  
  342.  
  343. <li><strong>Examples:</strong> See <a href="https://github.com/domdomegg/airtable-mcp-server">airtable-mcp-server (npm/docker/MCPB)</a>, <a href="https://github.com/domdomegg/time-mcp-nuget">time-mcp-nuget</a>, <a href="https://github.com/domdomegg/time-mcp-pypi">time-mcp-pypi</a>.</li>
  344. </ul>
  345.  
  346.  
  347.  
  348. <h2 class="wp-block-heading" id="automate-publishing-with-github-actions">Automate publishing with GitHub Actions</h2>
  349.  
  350.  
  351.  
  352. <p>You can automate publishing so every tagged release is published to both your package registry and the MCP registry.</p>
  353.  
  354.  
  355.  
  356. <p>Create <code>.github/workflows/publish-mcp.yml</code>:</p>
  357.  
  358.  
  359.  
  360. <pre class="wp-block-code language-plaintext"><code>name: Publish to MCP Registry
  361. on:
  362.  push:
  363.    tags: ["v*"]
  364.  
  365. jobs:
  366.  publish:
  367.    runs-on: ubuntu-latest
  368.    permissions:
  369.      id-token: write  # For OIDC
  370.      contents: read
  371.  
  372.    steps:
  373.      - uses: actions/checkout@v5
  374.  
  375.      # (Edit these for your package type)
  376.      - name: Setup Node.js
  377.        uses: actions/setup-node@v5
  378.        with:
  379.          node-version: "lts/*"
  380.      - name: Install dependencies
  381.        run: npm ci
  382.      - name: Build and test
  383.        run: |
  384.          npm run build --if-present
  385.          npm run test --if-present
  386.      - name: Publish to npm
  387.        run: npm publish
  388.        env:
  389.          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
  390.  
  391.      # MCP publishing (works for all package types)
  392.      - name: Download MCP Publisher
  393.        run: |
  394.          curl -L "https://github.com/modelcontextprotocol/registry/releases/download/latest/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
  395.      - name: Publish to MCP Registry
  396.        run: |
  397.          ./mcp-publisher login github-oidc
  398.          ./mcp-publisher publish
  399.  
  400.      # Optional: keep server.json version in sync with git tag
  401.      - run: |
  402.          VERSION=${GITHUB_REF#refs/tags/v}
  403.          jq --arg v "$VERSION" '.version = $v' server.json &gt; tmp &amp;&amp; mv tmp server.json</code></pre>
  404.  
  405.  
  406.  
  407. <p>To trigger the workflow:</p>
  408.  
  409.  
  410.  
  411. <pre class="wp-block-code language-plaintext"><code>git tag v1.0.0
  412. git push origin v1.0.0</code></pre>
  413.  
  414.  
  415.  
  416. <p>When you publish, your server shows up in the open source registry and downstream registries (like GitHub&rsquo;s) automatically pick up updates. No more notifying a dozen different registries every time you ship a new version.</p>
  417.  
  418.  
  419.  
  420. <p>&#9989; <strong>Pro tips:</strong></p>
  421.  
  422.  
  423.  
  424. <ul class="wp-block-list">
  425. <li>Host your code in a <strong>public GitHub repository</strong> to show verified ownership.</li>
  426.  
  427.  
  428.  
  429. <li>Add tags in <code>server.json</code> so developers can easily discover your server by category.</li>
  430.  
  431.  
  432.  
  433. <li>Updates propagate automatically downstream&mdash;no manual notifications required</li>
  434. </ul>
  435.  
  436.  
  437.  
  438. <p><strong>How to manage MCP servers in the enterprise</strong></p>
  439.  
  440.  
  441.  
  442. <p>If you&rsquo;re managing MCP usage across a large organization, governance isn&rsquo;t optional. You need control over which servers your developers can install&mdash;especially when those servers interact with sensitive data.</p>
  443.  
  444.  
  445.  
  446. <p>GitHub now supports <strong>registry allow lists</strong> so admins can control which MCP servers are available to developers.</p>
  447.  
  448.  
  449.  
  450. <p>Here are the steps for admins (which may be you!):</p>
  451.  
  452.  
  453.  
  454. <ol class="wp-block-list">
  455. <li>Stand up or connect an internal registry that follows the MCP API spec (registry + HTTP endpoint).</li>
  456.  
  457.  
  458.  
  459. <li>Add vetted MCP servers (internal + external) to your registry.</li>
  460.  
  461.  
  462.  
  463. <li>Point GitHub Enterprise settings to that registry endpoint.</li>
  464.  
  465.  
  466.  
  467. <li>MCP-aware surfaces (starting with VS Code) enforce the allow list automatically.</li>
  468. </ol>
  469.  
  470.  
  471.  
  472. <p><strong>Example: How the allow list works</strong></p>
  473.  
  474.  
  475.  
  476. <p>Your internal registry at <code>https://internal.mybank.com/mcp-registry</code> returns:</p>
  477.  
  478.  
  479.  
  480. <pre class="wp-block-code"><code>{
  481.  "servers": [
  482.    {
  483.      "name": "github.com/github/mcp-server",
  484.      "version": "1.0.0"
  485.    },
  486.    {
  487.      "name": "github.com/microsoft/markitdown-mcp",
  488.      "version": "2.1.0"
  489.    },
  490.    {
  491.      "name": "internal.mybank.com/mcp-servers/custom-tools",
  492.      "version": "1.5.0"
  493.    }
  494.  ]
  495. }</code></pre>
  496.  
  497.  
  498.  
  499. <p>When developers try to install an MCP server in VS Code, GitHub checks your registry endpoint and only allows installations from your approved list.</p>
  500.  
  501.  
  502.  
  503. <p>This governance model means you can vet partnerships, run security scans, and maintain compliance, all while giving developers access to the tools they need.</p>
  504.  
  505.  
  506.  
  507. <p>&#9989; <strong>Pro tip:</strong> Use GitHub&rsquo;s API or your existing security pipeline to vet MCP servers before adding them to your allow list.</p>
  508.  
  509.  
  510.  
  511. <h2 class="wp-block-heading" id="tips-and-tricks-for-power-users">Tips and tricks for power users</h2>
  512.  
  513.  
  514.  
  515. <p>Once you&rsquo;ve got the basics down, here are some shortcuts to get more out of the registry:</p>
  516.  
  517.  
  518.  
  519. <ul class="wp-block-list">
  520. <li><strong>Sort smarter</strong>: Use GitHub stars and org verification to quickly assess quality and legitimacy. If a server has thousands of stars and comes from a verified org like Microsoft or HashiCorp, that&rsquo;s a strong signal.</li>
  521.  
  522.  
  523.  
  524. <li><strong>Local testing</strong>: Test your MCP server before publishing using the<a href="https://github.com/modelcontextprotocol/inspector"> MCP Inspector</a>. This helps you catch issues early without polluting the registry.&nbsp;</li>
  525.  
  526.  
  527.  
  528. <li><strong>Agent synergy</strong>: Copilot coding agent comes preloaded with GitHub and Playwright MCP servers. This combo enables auto-generated pull requests with screenshots of web apps, perfect for UI-heavy projects where visual validation matters.</li>
  529.  
  530.  
  531.  
  532. <li><strong>Tool overload fix</strong>: VS Code is rolling out semantic tool lookups, so your agent won&rsquo;t flood contexts with 90+ tools. Instead, only the relevant ones surface based on your prompt. This makes working with large MCP servers like GitHub&rsquo;s much more manageable.</li>
  533. </ul>
  534.  
  535.  
  536.  
  537. <h2 class="wp-block-heading" id="whats-next">What&rsquo;s next?</h2>
  538.  
  539.  
  540.  
  541. <p>The GitHub MCP Registry is just getting started. Here&rsquo;s a look at what&rsquo;s on the horizon&mdash;from self-publication to enterprise adoption&mdash;so you can see where the ecosystem is heading.</p>
  542.  
  543.  
  544.  
  545. <ul class="wp-block-list">
  546. <li><strong>Self-publication</strong>: Expected in the next couple months. This will unlock community-driven growth and make the registry the canonical source for all public MCP servers.</li>
  547.  
  548.  
  549.  
  550. <li><strong>More IDE support</strong>: Other IDEs are coming. The goal is to make MCP server installation seamless regardless of where you write code.</li>
  551.  
  552.  
  553.  
  554. <li><strong>Enterprise features</strong>: Governance flows to help unlock MCP usage in regulated industries. Think financial services, healthcare, and other sectors where compliance isn&rsquo;t negotiable.</li>
  555.  
  556.  
  557.  
  558. <li><strong>Agentic workflows</strong>: GitHub MCP server will start bundling tools into use-case-driven flows (e.g., &ldquo;analyze repository + open pull request&rdquo;) instead of just exposing raw API endpoints. This will make complex workflows feel like simple commands.</li>
  559. </ul>
  560.  
  561.  
  562.  
  563. <h2 class="wp-block-heading" id="get-started-today">Get started today</h2>
  564.  
  565.  
  566.  
  567. <p>The GitHub MCP Registry has 44 servers today and will continue growing (trust us!).</p>
  568.  
  569.  
  570.  
  571. <p>&#128073; Explore the <a href="https://github.com/mcp?utm_source=blog-source&amp;utm_campaign=mcp-registry-server-launch-2025">MCP Registry</a> on GitHub<a href="https://github.com/mcp?utm_source=blog-source&amp;utm_campaign=mcp-registry-server-launch-2025"><br></a>&#128073; To nominate your server now, email <strong>partnerships@github.com</strong>.</p>
  572.  
  573.  
  574.  
  575. <p>Soon, this registry will become the single source of truth for MCP servers, giving you one place to discover, install, and govern tools without hopping across outdated registries.</p>
  576.  
  577.  
  578.  
  579. <p>The future of AI-assisted development isn&rsquo;t about coding faster. It&rsquo;s about orchestrating tools that amplify your impact. And the GitHub MCP Registry is where that orchestration begins.</p>
  580. </body></html>
  581. <p>The post <a href="https://github.blog/ai-and-ml/generative-ai/how-to-find-install-and-manage-mcp-servers-with-the-github-mcp-registry/">How to find, install, and manage MCP servers with the GitHub MCP Registry</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  582. ]]></content:encoded>
  586. <post-id xmlns="com-wordpress:feed-additions:1">91673</post-id> </item>
  587. <item>
  588. <title>The road to better completions: Building a faster, smarter GitHub Copilot with a new custom model</title>
  589. <link>https://github.blog/ai-and-ml/github-copilot/the-road-to-better-completions-building-a-faster-smarter-github-copilot-with-a-new-custom-model/</link>
  591. <dc:creator><![CDATA[Shengyu Fu]]></dc:creator>
  592. <pubDate>Thu, 23 Oct 2025 18:31:12 +0000</pubDate>
  593. <category><![CDATA[AI & ML]]></category>
  594. <category><![CDATA[GitHub Copilot]]></category>
  595. <category><![CDATA[AI agents]]></category>
  596. <category><![CDATA[AI coding tools]]></category>
  597. <category><![CDATA[LLM]]></category>
  598. <guid isPermaLink="false">https://github.blog/?p=91797</guid>
  599.  
  600. <description><![CDATA[<p>Find out about the latest custom models powering the completions experience in GitHub Copilot. </p>
  601. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/the-road-to-better-completions-building-a-faster-smarter-github-copilot-with-a-new-custom-model/">The road to better completions: Building a faster, smarter GitHub Copilot with a new custom model</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  602. ]]></description>
  603. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  604. <html><body><p>Code completion remains the most widely used GitHub Copilot feature, helping millions of developers stay in the flow every day. Our team has continuously iterated on the custom models powering the completions experience in GitHub Copilot driven by developer feedback. That work has had a big impact on giving you faster, more relevant suggestions in the editor.&nbsp;&nbsp;</p>
  605.  
  606.  
  607.  
  608. <p>We&rsquo;re now delivering suggestions with 20% more accepted and retained characters, 12% higher acceptance rate, 3x higher token-per-second throughput, and a 35% reduction in latency.&nbsp;</p>
  609.  
  610.  
  611.  
  612. <p>These updates now power GitHub Copilot across editors and environments. We&rsquo;d like to share our journey on how we trained and evaluated our custom model for code completions.&nbsp;</p>
  613.  
  614.  
  615.  
  616. <h2 class="wp-block-heading" id="h-why-it-matters-nbsp">Why it matters&nbsp;</h2>
  617.  
  618.  
  619.  
  620. <p>When Copilot completions improve, you spend less time editing and more time building. The original Copilot was optimized for the highest acceptance rate possible. However, we realized that a heavy focus on acceptance rates could lead to incorrectly favoring a high volume of simple and short suggestions.&nbsp;&nbsp;</p>
  621.  
  622.  
  623.  
  624. <p>We heard your feedback that this didn&rsquo;t reflect real developer needs or deliver the highest quality experience. So, we pivoted to also optimize for accepted and retained characters, code flow, and other metrics.&nbsp;</p>
  625.  
  626.  
  627.  
  628. <ul class="wp-block-list">
  629. <li><strong>20% higher accepted-and-retained characters</strong> results in more of each Copilot suggestion staying in your final code, not just ending up temporarily accepted and deleted later. In other words, suggestions provide more value with fewer keystrokes.</li>
  630.  
  631.  
  632.  
  633. <li><strong>12% higher acceptance rate</strong> means you find suggestions more useful more often, reflecting better immediate utility.&nbsp;</li>
  634.  
  635.  
  636.  
  637. <li><strong>3x throughput</strong> <strong>with 35% lower latency</strong> makes Copilot feel faster. It handles more requests at once while keeping your coding flow unbroken (throughput describes how much work the system can handle overall, while latency describes how quickly each individual request completes).</li>
  638. </ul>
  639.  
  640.  
  641.  
  642. <h2 class="wp-block-heading" id="h-how-we-evaluate-custom-models-nbsp">How we evaluate custom models&nbsp;</h2>
  643.  
  644.  
  645.  
  646. <p>Copilot models are evaluated using combined signals from <strong>offline</strong>, <strong>pre-production</strong>, and <strong>production</strong> evaluations. Each layer helps us refine different aspects of the experience while ensuring better quality in real developer workflows.&nbsp;</p>
  647.  
  648.  
  649.  
  650. <h3 class="wp-block-heading" id="h-1-offline-evaluations-nbsp-nbsp">1) Offline evaluations&nbsp;&nbsp;</h3>
  651.  
  652.  
  653.  
  654. <p><strong>Execution-based benchmark: </strong>As part of our offline evaluations, we first test against internal and public repositories with strong code by unit test and scenario coverage, spanning all major languages. Each test simulates real tasks, accepts suggestions, and measures build-and-test pass rates. This emphasizes functional correctness over surface fluency.&nbsp;&nbsp;</p>
  655.  
  656.  
  657.  
  658. <p>Below is an example of a partial token completion error: the model produced <code>data<strong>et</strong></code> instead of <code>data<strong>set</strong></code>.</p>
  659.  
  660.  
  661.  
  662. <figure class="wp-block-image size-large"><img data-recalc-dims="1" fetchpriority="high" decoding="async" height="447" width="1024" src="https://github.blog/wp-content/uploads/2025/10/partial-token-completion-error.png?resize=1024%2C447" alt="Screenshot of a Python code editor showing a function named resolve_file inside a file called dataset_utilities.py. The function takes two string arguments, dataset and filename, and returns a string. The purpose, according to the docstring, is to resolve a file from a dataset and assert that only one file is found. The code uses os.path and glob to find files. There&rsquo;s a highlighted line path = os.path.join(dat... with an error under dat, suggesting a variable name typo (dat instead of dataset). Several red underlines indicate syntax or reference errors in the code." class="wp-image-91828" srcset="https://github.blog/wp-content/uploads/2025/10/partial-token-completion-error.png?w=1026 1026w, https://github.blog/wp-content/uploads/2025/10/partial-token-completion-error.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/partial-token-completion-error.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/partial-token-completion-error.png?w=1024 1024w" sizes="(max-width: 1000px) 100vw, 1000px" /></figure>
  663.  
  664.  
  665.  
  666. <p><strong>LLM-judge scoring: </strong>While we start with execution-based evaluation, this has downsides: it only tells if the code will compile, but the results are not always aligned with developer preferences. To ensure the best possible outcomes, we run an independent LLM to score completions across three axes:&nbsp;&nbsp;</p>
  667.  
  668.  
  669.  
  670. <ul class="wp-block-list">
  671. <li><strong>Quality:</strong> Ensure syntax validity, duplication/overlap, format and style consistency.&nbsp;</li>
  672.  
  673.  
  674.  
  675. <li><strong>Relevance: </strong>Focus on relevant code, avoid hallucination and overreach.&nbsp;</li>
  676.  
  677.  
  678.  
  679. <li><strong>Helpfulness:</strong> Reduce manual effort, avoid outdated or deprecated APIs.&nbsp;</li>
  680. </ul>
  681.  
  682.  
  683.  
  684. <h3 class="wp-block-heading" id="h-2-pre-production-evaluations-qualitative-dogfooding-nbsp">2) Pre-production evaluations: Qualitative dogfooding&nbsp;</h3>
  685.  
  686.  
  687.  
  688. <p>Our next step includes working with internal developers and partners to test models side-by-side in real workflows (to do the latter, we exposed the preview model to developers through Copilot&rsquo;s model picker). We collect structured feedback on readability, trust, and &ldquo;taste.&rdquo; Part of this process includes working with language experts to improve overall completion quality. This is unique: while execution-based testing, LLM-based evaluations, dogfood testing, and A/B testing are common, we find language-specific evaluations lead to better outcomes along quality and style preferences.&nbsp;</p>
  689.  
  690.  
  691.  
  692. <h3 class="wp-block-heading" id="h-3-production-based-evaluations-a-b-testing-nbsp">3) Production-based evaluations: A/B testing&nbsp;</h3>
  693.  
  694.  
  695.  
  696. <p>Ultimately, the lived experience of developers like you is what matters most. We measure improvements using accepted-and-retained characters, acceptance rates, completion-shown rate, time-to-first token, latency, and many other metrics. We ship only when statistically significant improvements hold up under real developer workloads.&nbsp;</p>
  697.  
  698.  
  699.  
  700. <h2 class="wp-block-heading" id="h-how-we-trained-our-new-copilot-completions-model-nbsp">How we trained our new Copilot completions model&nbsp;</h2>
  701.  
  702.  
  703.  
  704. <h3 class="wp-block-heading" id="h-mid-training-nbsp">Mid-training&nbsp;</h3>
  705.  
  706.  
  707.  
  708. <p>Modern codebases use modern APIs. Before fine-tuning, we build a code-specific foundational model via mid-training using a curated, de-duplicated corpus of modern, idiomatic, public, and internal code with nearly 10M repositories and 600-plus programming languages. (Mid-training refers to the stage after the base model has been pretrained on a very large, diverse corpus, but before it undergoes final fine-tuning or instruction-tuning).&nbsp;</p>
  709.  
  710.  
  711.  
  712. <p>This is a critical step to ensure behaviors, new language syntax, and recent API versions are utilized by the model. We then use supervised fine-<s> </s>tuning and reinforcement learning while mixing objectives beyond next-token prediction&mdash;span infillings and docstring/function pairs&mdash;so the model learns structure, naming, and intent, not just next-token prediction. This helps us make the foundational model code-fluent, style-consistent, and context-aware, ready for more targeted fine-tuning via supervised fine-tuning.&nbsp;</p>
  713.  
  714.  
  715.  
  716. <h3 class="wp-block-heading" id="h-supervised-fine-tuning-nbsp">Supervised fine-tuning&nbsp;</h3>
  717.  
  718.  
  719.  
  720. <p>Newer general-purpose chat models perform well in natural language to generate code, but underperform on fill-in-the-middle (FIM) code completion. In practice, chat models experience cursor-misaligned inserts, duplication of code before the cursor (prefix), and overwrites of code after the cursor (suffix).&nbsp;&nbsp;</p>
  721.  
  722.  
  723.  
  724. <p>As we moved to fine-tuned behaviors, we trained models specialized in completions by way of synthetic fine-tuning to behave like a great FIM engine. In practice, this improves:&nbsp;</p>
  725.  
  726.  
  727.  
  728. <ul class="wp-block-list">
  729. <li><strong>Prefix/suffix awareness</strong>: Accurate inserts between tokens, mid-line continuations, full line completions, and multi-line block completions without trampling the suffix.&nbsp;</li>
  730.  
  731.  
  732.  
  733. <li><strong>Formatting fidelity</strong>: Respect local style (indentation, imports, docstrings) and avoid prefix duplication.&nbsp;</li>
  734. </ul>
  735.  
  736.  
  737.  
  738. <p>The result is significantly improved FIM performance. For example, here is a benchmark comparing our latest completions model to GPT-4.1-mini on <a href="https://github.com/openai/human-eval-infilling" target="_blank" rel="noreferrer noopener">OpenAI&rsquo;s HumanEval Infilling Benchmarks</a>.&nbsp;&nbsp;</p>
  739.  
  740.  
  741.  
  742. <figure class="wp-block-image size-large"><img data-recalc-dims="1" decoding="async" height="538" width="1024" src="https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?resize=1024%2C538" alt="A chart showing HumanEval Infilling Benchmarks for two different AI models. These include a custom model from GitHub named Copilot Completions and OpenAI's GPT-4o-mini. The evaluations show superior performance across single line, multi line, random span, and random span light tests for the Copilot Completions model. " class="wp-image-91837" srcset="https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=2400 2400w, https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=1536 1536w, https://github.blog/wp-content/uploads/2025/10/HumanEvalInfilling_1200x630.png?w=2048 2048w" sizes="(max-width: 1000px) 100vw, 1000px" /></figure>
  743.  
  744.  
  745.  
  746. <h3 class="wp-block-heading" id="h-reinforcement-learning-nbsp">Reinforcement learning&nbsp;</h3>
  747.  
  748.  
  749.  
  750. <p>Finally, we used a custom reinforcement learning algorithm, teaching the model through rewards and penalties to internalize what makes code suggestions useful in real developer scenarios along three axes:</p>
  751.  
  752.  
  753.  
  754. <ul class="wp-block-list">
  755. <li><strong>Quality</strong>: Syntax-valid, compilable code that follows project style (indentations, imports, headers).&nbsp;&nbsp;</li>
  756.  
  757.  
  758.  
  759. <li><strong>Relevance</strong>: On-task suggestions that respect surrounding context and the file&rsquo;s intent.&nbsp;&nbsp;</li>
  760.  
  761.  
  762.  
  763. <li><strong>Helpfulness</strong>: Suggestions that reduce manual effort and prefer modern APIs.&nbsp;&nbsp;</li>
  764. </ul>
  765.  
  766.  
  767.  
  768. <p>Together, these create completions that are correct, relevant, and genuinely useful at the cursor instead of being verbose or superficially helpful.&nbsp;</p>
  769.  
  770.  
  771.  
  772. <h2 class="wp-block-heading" id="h-what-we-learned-nbsp">What we learned&nbsp;</h2>
  773.  
  774.  
  775.  
  776. <p>After talking with programming language experts and finding success in our prompt-based<s> </s>approach, one of our most important lessons was adding related files like C++ header files to our training data. Beyond this, we also came away with three key learnings:&nbsp;</p>
  777.  
  778.  
  779.  
  780. <ul class="wp-block-list">
  781. <li><strong>Reward carefully: </strong>Early reinforcement learning version over-optimized for longer completions, adding too many comments in the form of &ldquo;reward hacking.&rdquo; To mitigate this problem, we introduced comment guardrails to keep completions concise and focused on moving the task forward while penalizing unnecessary commentary.&nbsp;</li>
  782.  
  783.  
  784.  
  785. <li><strong>Metrics matter: </strong>Being hyper-focused on a metric like acceptance rate can lead to experiences that look good on paper, but do not result in happy developers. That makes it critical to evaluate performance by monitoring multiple metrics with real-world impact.</li>
  786.  
  787.  
  788.  
  789. <li><strong>Train for real-world usage: </strong>We align our synthetic fine-tuning data with real-world usage and adapt our training accordingly. This helps us identify problematic patterns and remove them via training to improve real-world outcomes.&nbsp;&nbsp;</li>
  790. </ul>
  791.  
  792.  
  793.  
  794. <h2 class="wp-block-heading" id="h-what-s-next-nbsp">What&rsquo;s next&nbsp;</h2>
  795.  
  796.  
  797.  
  798. <p>We&rsquo;re continuing to push the frontier of Copilot completions by:&nbsp;</p>
  799.  
  800.  
  801.  
  802. <ul class="wp-block-list">
  803. <li>Expanding into domain-specific slices (e.g., game engines, financial, ERP).&nbsp;</li>
  804.  
  805.  
  806.  
  807. <li>Refining reward functions for build/test success, semantic usefulness (edits that advance the user&rsquo;s intent without bloat), and API modernity preference for up-to-date, idiomatic libraries and patterns. This is helping us shape completion behavior with greater precision.&nbsp;</li>
  808.  
  809.  
  810.  
  811. <li>Driving faster, cheaper, higher-quality completions across all developer environments.&nbsp;&nbsp;</li>
  812. </ul>
  813.  
  814.  
  815.  
  816. <div class="wp-block-group post-content-cta has-global-padding is-layout-constrained wp-block-group-is-layout-constrained">
  817. <p>Experience faster, smarter code completions yourself. <a href="https://github.com/features/copilot" target="_blank" rel="noreferrer noopener">Try GitHub Copilot in VS Code &gt;</a>&nbsp;</p>
  818. </div>
  819.  
  820.  
  821.  
  822. <h3 class="wp-block-heading" id="h-acknowledgments-nbsp">Acknowledgments&nbsp;</h3>
  823.  
  824.  
  825.  
  826. <p>First, a big shoutout to our developer community for continuing to give us feedback and push us to deliver the best possible experiences with GitHub Copilot. Moreover, a huge thanks to the researchers, engineers, product managers, designers across GitHub and Microsoft who curated the training data, built the training pipeline, evaluation suites, client and serving stack<s> </s>&mdash;<s> </s>and to the GitHub Copilot product and engineering teams for smooth model releases.&nbsp;</p>
  827. </body></html>
  828. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/the-road-to-better-completions-building-a-faster-smarter-github-copilot-with-a-new-custom-model/">The road to better completions: Building a faster, smarter GitHub Copilot with a new custom model</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  829. ]]></content:encoded>
  833. <post-id xmlns="com-wordpress:feed-additions:1">91797</post-id> </item>
  834. <item>
  835. <title>From karaoke terminals to AI résumés: The winners of GitHub’s For the Love of Code challenge</title>
  836. <link>https://github.blog/open-source/from-karaoke-terminals-to-ai-resumes-the-winners-of-githubs-for-the-love-of-code-challenge/</link>
  838. <dc:creator><![CDATA[Lee Reilly]]></dc:creator>
  839. <pubDate>Wed, 22 Oct 2025 20:30:35 +0000</pubDate>
  840. <category><![CDATA[Open Source]]></category>
  841. <category><![CDATA[developer experience]]></category>
  842. <category><![CDATA[open source]]></category>
  843. <category><![CDATA[open source community]]></category>
  844. <guid isPermaLink="false">https://github.blog/?p=91749</guid>
  845.  
  846. <description><![CDATA[<p>This summer, we invited devs to participate in our hackathon for joyful, ridiculous, and wildly creative projects. Here are the winners of For the Love of Code!</p>
  847. <p>The post <a href="https://github.blog/open-source/from-karaoke-terminals-to-ai-resumes-the-winners-of-githubs-for-the-love-of-code-challenge/">From karaoke terminals to AI résumés: The winners of GitHub’s For the Love of Code challenge</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  848. ]]></description>
  849. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  850. <html><body><p>Every developer has that project they build just for the fun of it. You know how it goes: you start by asking &ldquo;what if?&rdquo; and then you have something weird and wonderful hours later.&nbsp;</p>
  851.  
  852.  
  853.  
  854. <p>This summer, we decided to celebrate that spirit with <a href="https://github.blog/open-source/for-the-love-of-code-2025/"><strong>For the Love of Code</strong></a>, our first-ever competition for projects built purely for fun. More than 300 developers answered the call. Some leaned on GitHub Copilot to refactor ideas, fix bugs, and spark inspiration. Some teamed up. Others flew solo, guided only by caffeine and curiosity.</p>
  855.  
  856.  
  857.  
  858. <p>Entries spanned everything from a <a href="https://github.com/cyprieng/github-breakout">Breakout game powered by your GitHub graph</a>, to a <a href="https://github.com/sanaysarthak/git-laugh-track">laugh-track that plays on every commit</a>, <a href="https://github.com/NeoKish/vscode-yelp-style-reviewer">a Yelp-style code reviewer in VS Code</a> &#9733;&#9733;&#9733;&#9733;&#9734;, a <a href="https://github.com/leereilly/copilot-cam">Copilot you can literally see on camera</a>, and even a <a href="https://github.com/GustyCube/pr-notes-comic-strip">comic strip made from your release notes</a>.</p>
  859.  
  860.  
  861.  
  862. <p>We invited participants to build anything that sparks joy across six whimsical categories:</p>
  863.  
  864.  
  865.  
  866. <ul class="wp-block-list">
  867. <li><strong>&#128280; Buttons, beeps &amp; blinkenlights:</strong> Hardware hacks, LEDs, sensors, and gadgets galore.</li>
  868.  
  869.  
  870.  
  871. <li>&#128421;&#65039;<strong> Terminal talent: </strong>Command-line creations and retro computing love letters.</li>
  872.  
  873.  
  874.  
  875. <li><strong>&#127760; World wide wonders: </strong>Browser-based experiments, apps, and interactive art.</li>
  876.  
  877.  
  878.  
  879. <li><strong>&#129302; Agents of change:</strong> AI, bots, and automation with heart.</li>
  880.  
  881.  
  882.  
  883. <li><strong>&#128377;&#65039; Game on: </strong>Games big or small, serious or silly.</li>
  884.  
  885.  
  886.  
  887. <li>&#127183;<strong> Everything but the kitchen sink: </strong>The wildcard (if it doesn&rsquo;t fit anywhere else, it fits here).</li>
  888. </ul>
  889.  
  890.  
  891.  
  892. <aside data-color-mode="light" data-dark-theme="dark" data-light-theme="light_dimmed" class="wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--1" style="border-top-width:4px">
  893. <h3 class="wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5" id="h-how-github-copilot-powered-creativity" style="margin-top:0">&#128161; How GitHub Copilot powered creativity</h3>
  894.  
  895.  
  896.  
  897. <p><a href="https://github.com/features/copilot">GitHub Copilot</a> helped contest participants:</p>
  898.  
  899.  
  900.  
  901. <ul class="wp-block-list">
  902. <li>Create efficient Go code to integrate with the GitHub API</li>
  903.  
  904.  
  905.  
  906. <li>Scaffold repetitive code and boilerplate</li>
  907.  
  908.  
  909.  
  910. <li>Suggest API calls and syntax corrections</li>
  911.  
  912.  
  913.  
  914. <li>Debug hardware quirks and runtime errors</li>
  915.  
  916.  
  917.  
  918. <li>Spark inspiration for algorithms and UI design</li>
  919.  
  920.  
  921.  
  922. <li>Write their first Python program</li>
  923.  
  924.  
  925.  
  926. <li>Make their first real push to GitHub</li>
  927. </ul>
  928.  
  929.  
  930.  
  931. <p>And it didn&rsquo;t stop there. When creativity met Copilot, side projects turned into something spectacular.<br><br><a href="https://github.blog/ai-and-ml/github-copilot/copilot-faster-smarter-and-built-for-how-you-work-now/">Discover how Copilot can help you with your project &gt;</a></p>
  932. </aside>
  933.  
  934.  
  935.  
  936. <h2 class="wp-block-heading" id="meet-the-winners-open-source-experiments-ai-side-projects-and-more">Meet the winners: Open source experiments, AI side projects, and more</h2>
  937.  
  938.  
  939.  
  940. <p>Here are the top three entries from each category.</p>
  941.  
  942.  
  943.  
  944. <h2 class="wp-block-heading" id="%f0%9f%94%98-buttons-beeps-blinkenlights">&#128280; Buttons, beeps &amp; blinkenlights&nbsp;</h2>
  945.  
  946.  
  947.  
  948. <h3 class="wp-block-heading" id="plane-tracker-diy-radar-on-your-desk">Plane Tracker: DIY radar on your desk</h3>
  949.  
  950.  
  951.  
  952. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="1024" width="771" src="https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?resize=771%2C1024" alt="A person holding an Adafruit TFT Gizmo display connected to a laptop. The screen shows a green radar interface with red blips representing nearby planes. In the background, Python code and a terminal window in VS Code display mock plane data being sent via Bluetooth." class="wp-image-91771" srcset="https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=1656 1656w, https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=226 226w, https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=771 771w, https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=1156 1156w, https://github.blog/wp-content/uploads/2025/10/plane-tracker.jpg?w=1542 1542w" sizes="auto, (max-width: 771px) 100vw, 771px" /></figure>
  953.  
  954.  
  955.  
  956. <p><a href="https://github.com/cpstroum/flight-tracker-bluefruit">Plane Tracker</a> by @cpstroum is a DIY radar that uses an <a href="https://learn.adafruit.com/introducing-circuit-playground/overview?gad_source=1&amp;gad_campaignid=21079267614&amp;gbraid=0AAAAADx9JvS9gzUjK958dRkUNTd_N30et&amp;gclid=Cj0KCQjw9czHBhCyARIsAFZlN8RtFMPe77bX67pkLaGHs37V1Nq0iJBnTNQ47Vuex2Y-oozA28_oRmsaAhPqEALw_wcB">Adafruit Circuit Playground</a>, Bluetooth, and the ADS-B Exchange API to fetch live flight data. It turns nearby planes into a real-time mini radar display.</p>
  957.  
  958.  
  959.  
  960. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @cpstroum with Git itself and with structuring the initial project for their first real push to GitHub. Thanks, Copilot! And welcome aboard, @cpstroum!
  961.  
  962.  
  963.  
  964. <h3 class="wp-block-heading" id="h-cadrephoto-the-easy-e-ink-photo-frame">Cadrephoto: The easy e-ink photo frame</h3>
  965.  
  966.  
  967.  
  968. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="512" width="1024" src="https://github.blog/wp-content/uploads/2025/10/cadrephoto.png?resize=1024%2C512" alt="A wooden e-ink photo frame displays a grayscale version of &ldquo;Girl with a Pearl Earring.&rdquo; A smartphone next to it shows an email being sent with the same image, and a red arrow points from the phone to the frame, illustrating how the photo is updated remotely." class="wp-image-91770" srcset="https://github.blog/wp-content/uploads/2025/10/cadrephoto.png?w=1280 1280w, https://github.blog/wp-content/uploads/2025/10/cadrephoto.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/cadrephoto.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/cadrephoto.png?w=1024 1024w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  969.  
  970.  
  971.  
  972. <p><a href="https://github.com/ozh/cadrephoto">Cadrephoto</a> by @ozh is a Raspberry Pi and e-ink photo frame that displays pictures emailed to it (no app, no setup, perfect for less tech-savvy people). It checks an inbox, downloads the latest photo, and updates the screen automatically.</p>
  973.  
  974.  
  975.  
  976. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @ozh with their first Python project. It worked smoothly inside JetBrains IDEs and made code completion feel almost like magic.
  977.  
  978.  
  979.  
  980. <h3 class="wp-block-heading" id="h-buildin-traffic-light-builds-for-your-repository">BuildIn: Traffic-light builds for your repository</h3>
  981.  
  982.  
  983.  
  984. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="1024" width="1024" src="https://github.blog/wp-content/uploads/2025/10/buildin.png?resize=1024%2C1024" alt="A collage of four photos showing an Arduino breadboard project with multiple jumper wires and LEDs in different colors&mdash;blue, green, yellow, and red&mdash;lit up during various testing stages." class="wp-image-91769" srcset="https://github.blog/wp-content/uploads/2025/10/buildin.png?w=1080 1080w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=150 150w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=600 600w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=400 400w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=200 200w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=1000 1000w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=90 90w, https://github.blog/wp-content/uploads/2025/10/buildin.png?w=116 116w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  985.  
  986.  
  987.  
  988. <p><a href="https://github.com/SUNSET-Sejong-University/BuildIn/">BuildIn</a> by @SUNSET-Sejong-University and @lepetitprince99 is a real-life traffic light for your code that sits on your desk. Using an Arduino and the GitHub API, it lights up red, yellow, green, or blue to show your repository&rsquo;s build status at a glance.</p>
  989.  
  990.  
  991.  
  992. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @SUNSET-Sejong-University debug and optimize their code. It saved time tracking down tricky hardware issues and made troubleshooting much easier.
  993.  
  994.  
  995.  
  996. <h2 class="wp-block-heading" id="h-terminal-talent">&#128421;&#65039; Terminal talent</h2>
  997.  
  998.  
  999.  
  1000. <h3 class="wp-block-heading" id="h-restohack-a-roguelike-resurrected-from-1984">RestoHack: A roguelike resurrected from 1984</h3>
  1001.  
  1002.  
  1003.  
  1004. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" width="582" height="422" src="https://github.blog/wp-content/uploads/2025/10/restohack.png?w=582&#038;resize=582%2C422" alt="A black terminal window displaying ASCII art of a tombstone reading &ldquo;REST IN PEACE mjh 0 AU killed by a giant rat 2025,&rdquo; from a retro text-based game." class="wp-image-91768" srcset="https://github.blog/wp-content/uploads/2025/10/restohack.png?w=582 582w, https://github.blog/wp-content/uploads/2025/10/restohack.png?w=300 300w" sizes="auto, (max-width: 582px) 100vw, 582px" /></figure>
  1005.  
  1006.  
  1007.  
  1008. <p><a href="https://github.com/Critlist/restoHack">RestoHack</a> by @Critlist resurrects the 1984 roguelike game that inspired <a href="https://github.com/NetHack/NetHack">NetHack</a>, rebuilt from the original source with modern tools and a preservationist&rsquo;s touch. It compiles cleanly, runs faithfully, and proves that forty years later, permadeath still hits hard.</p>
  1009.  
  1010.  
  1011.  
  1012. <h3 class="wp-block-heading" id="h-jukebox-cli">Jukebox CLI</h3>
  1013.  
  1014.  
  1015.  
  1016. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="466" width="1024" src="https://github.blog/wp-content/uploads/2025/10/jukebox.png?resize=1024%2C466" alt="A pixel art jukebox interface in a terminal-based music player. The screen shows colorful pixel graphics in the center, a playlist of songs on the right, and playback controls with progress and volume bars at the bottom." class="wp-image-91767" srcset="https://github.blog/wp-content/uploads/2025/10/jukebox.png?w=1780 1780w, https://github.blog/wp-content/uploads/2025/10/jukebox.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/jukebox.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/jukebox.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/jukebox.png?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1017.  
  1018.  
  1019.  
  1020. <p><a href="https://github.com/FedeCarollo/jukebox-cli">Jukebox CLI </a>by @FedeCarollo is a colorful, animated jukebox that runs right in your terminal. Built in Rust with Ratatui, it plays MP3s, shows floating musical notes, and color-codes each track in a scrollable playlist. You can play, pause, skip, and adjust the volume without ever leaving your command line.</p>
  1021.  
  1022.  
  1023.  
  1024. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @FedeCarollo explore unfamiliar Rust libraries and find their footing.
  1025.  
  1026.  
  1027.  
  1028. <h3 class="wp-block-heading" id="h-tuneminal-sing-your-commits-from-the-command-line">Tuneminal: Sing your commits from the command line</h3>
  1029.  
  1030.  
  1031.  
  1032. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="521" width="1024" src="https://github.blog/wp-content/uploads/2025/10/tuneminal.png?resize=1024%2C521" alt="A terminal-based karaoke interface titled &ldquo;Tuneminal.&rdquo; The screen displays a song library with &ldquo;IRIS &ndash; Kenshi Yonezu,&rdquo; current score and accuracy, and placeholders for lyrics and an audio visualizer." class="wp-image-91766" srcset="https://github.blog/wp-content/uploads/2025/10/tuneminal.png?w=1279 1279w, https://github.blog/wp-content/uploads/2025/10/tuneminal.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/tuneminal.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/tuneminal.png?w=1024 1024w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1033.  
  1034.  
  1035.  
  1036. <p><a href="https://github.com/heza-ru/Tuneminal">Tuneminal</a> by @heza-ru turns your terminal into a full-blown karaoke stage with scrolling lyrics, live audio visualization, and scoring that rewards your inner rock star. It&rsquo;s open source, cross-platform, and the perfect excuse to sing while that <code>git clone</code> takes a while.</p>
  1037.  
  1038.  
  1039.  
  1040. <h2 class="wp-block-heading" id="h-world-wide-wonders">&#127760; World wide wonders</h2>
  1041.  
  1042.  
  1043.  
  1044. <h3 class="wp-block-heading" id="h-netstalgia-surf-the-90s-web-on-virtual-dial-up">Netstalgia: Surf the &lsquo;90s web on virtual dial-up</h3>
  1045.  
  1046.  
  1047.  
  1048. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="640" width="1024" src="https://github.blog/wp-content/uploads/2025/10/netstalgia.png?resize=1024%2C640" alt="A retro 1990s-style web page called &ldquo;Netsalgia.com&rdquo; designed to look like a Windows 95 desktop. The page features colorful buttons, visitor counters, fake ads, and a pop-up asking users to star the GitHub repository for this nostalgic project." class="wp-image-91765" srcset="https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=3584 3584w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=1536 1536w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=2048 2048w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=288 288w, https://github.blog/wp-content/uploads/2025/10/netstalgia.png?w=3000 3000w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1049.  
  1050.  
  1051.  
  1052. <p><a href="https://github.com/heza-ru/Netstalgia">Netstalgia</a> by @heza-ru (again!) is a fully functional &lsquo;90s web fever dream built with modern tech, but visually stuck on virtual dial-up. It&rsquo;s got dancing babies, popup ads, a fake BBS, and more CRT glow than your old Gateway 2000 ever survived.</p>
  1053.  
  1054.  
  1055.  
  1056. <p>In true retro internet spirit, it even ships with a fake GitHub Star Ransomware&mdash;a tongue-in-cheek &ldquo;virus&rdquo; that demands you star the repo to &ldquo;decrypt your files.&rdquo; A clever (and harmless) new twist on the eternal quest for GitHub stars. &#11088;&#128190;</p>
  1057.  
  1058.  
  1059.  
  1060. <h3 class="wp-block-heading" id="bionic-reader-speed-read-your-screen">Bionic Reader: Speed read your screen</h3>
  1061.  
  1062.  
  1063.  
  1064. <p><a href="https://github.com/Awesome-XV/Bionic-Reader">Bionic Reader</a> by @Awesome-XV rewires how you read by bolding the first few letters of each word so your brain fills in the rest. It&rsquo;s like giving your eyes a speed boost without the caffeine jitters to read faster than ever.</p>
  1065.  
  1066.  
  1067.  
  1068. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @Awesome-XV write project documentation and scaffold the initial codebase.
  1069.  
  1070.  
  1071.  
  1072. <h3 class="wp-block-heading" id="h-the-git-roast-show-roast-your-github-profile-lovingly">The Git Roast Show: Roast your GitHub profile&hellip; lovingly</h3>
  1073.  
  1074.  
  1075.  
  1076. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="640" width="1024" src="https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?resize=1024%2C640" alt="A stylized image featuring a cartoon GitHub Octocat character in a tuxedo and sunglasses holding a microphone. The text above reads &ldquo;The GitRoast Show,&rdquo; and a speech bubble says &ldquo;we don&rsquo;t fork around here.&rdquo; The background has a swirling teal marble texture." class="wp-image-91764" srcset="https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=3584 3584w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=1536 1536w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=2048 2048w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=288 288w, https://github.blog/wp-content/uploads/2025/10/the-git-roast-show.png?w=3000 3000w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1077.  
  1078.  
  1079.  
  1080. <p><a href="https://github.com/rawrnuck/thegitroastshow">Git Roast Show</a> by @rawrnuck and @Anmol0201 is a full-stack web app that humorously &ldquo;roasts&rdquo; your GitHub profile. Built with React, Vite, and Express, it fetches live GitHub data to generate personalized, sound-enhanced, and animated comedy roasts.</p>
  1081.  
  1082.  
  1083.  
  1084. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @rawrnuck understand algorithms and handle the repetitive parts of their project.
  1085.  
  1086.  
  1087.  
  1088. <h3 class="wp-block-heading" id="nightlio-a-mood-tracker-you-actually-own">Nightlio: a mood tracker you actually own</h3>
  1089.  
  1090.  
  1091.  
  1092. <p><a href="https://github.com/shirsakm/nightlio">Nightlio</a> by @shirsakm is a privacy-first mood tracker and daily journal you can self-host in minutes. Log how you feel on a 5-point scale, add Markdown notes, tag entries like #Sleep or #Productivity, then explore calendars, streaks, and simple stats to spot patterns. It runs anywhere with Docker, stores data in a local SQLite file, and keeps things clean with JWT-protected APIs, a React/Vite front end, and optional Google OAuth. No ads. No subscriptions. Your server, your rules.</p>
  1093.  
  1094.  
  1095.  
  1096. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="484" width="1024" src="https://github.blog/wp-content/uploads/2025/10/nightlio.gif?resize=1024%2C484" alt="A dark-themed productivity app called Nightliio is shown in motion. The animation highlights mood tracking icons, personal goals such as &ldquo;Read Before Bed&rdquo; and &ldquo;Morning Meditation,&rdquo; and sections for adding goals, viewing history, and tracking progress through colorful animated bars." class="wp-image-91763"></figure>
  1097.  
  1098.  
  1099.  
  1100. <p><strong><em>Note</em></strong><em>: Because @heza-ru placed in two categories, we&rsquo;ve added a fourth winner to this category.</em></p>
  1101.  
  1102.  
  1103.  
  1104. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @shirsakm with refactors, color palette updates, and codebase-wide changes that would have taken much longer by hand.
  1105.  
  1106.  
  1107.  
  1108. <h2 class="wp-block-heading" id="%f0%9f%a4%96-agents-of-change">&#129302; Agents of change</h2>
  1109.  
  1110.  
  1111.  
  1112. <h3 class="wp-block-heading" id="neosgenesis-ai-that-thinks-about-thinking">Neosgenesis: AI that thinks about thinking</h3>
  1113.  
  1114.  
  1115.  
  1116. <p><a href="https://github.com/answeryt/Neosgenesis">Neosgenesis</a> by @answeryt is a metacognitive AI framework that teaches machines to think about how they think. It runs a five-stage loop (think, verify, learn, optimize, decide) while juggling multiple LLMs, tools, and real-time feedback. A multi-armed bandit picks the best reasoning patterns, and when it stalls, an &ldquo;aha&rdquo; mode explores fresh paths.</p>
  1117.  
  1118.  
  1119.  
  1120. <h3 class="wp-block-heading" id="medivision-assistant-accessible-ai-healthcare-for-all">MediVision Assistant: Accessible AI healthcare for all</h3>
  1121.  
  1122.  
  1123.  
  1124. <p><a href="https://github.com/omkardongre/medi-vision-assistant-ai">MediVision Assistant</a> by @omkardongre is an AI healthcare companion that helps elderly and disabled users manage their health through voice, image, and video. Users can scan medications, analyze skin conditions, log symptoms by voice, and chat with an AI doctor-like assistant.</p>
  1125.  
  1126.  
  1127.  
  1128. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @omkardongre generate React components, API templates, and AI integration code. It handled the boilerplate so they could focus on building features and improving the experience.
  1129.  
  1130.  
  1131.  
  1132. <h3 class="wp-block-heading" id="h-quiviva-the-resume-that-talks-back">Quiviva: The r&eacute;sum&eacute; that talks back</h3>
  1133.  
  1134.  
  1135.  
  1136. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="640" width="1024" src="https://github.blog/wp-content/uploads/2025/10/quiviva.png?resize=1024%2C640" alt="A colorful web interface titled &ldquo;An Interactive CV that Talks Back.&rdquo; The animation shows a chatbot window on the right where users can type questions to Kasia&rsquo;s AI-powered r&eacute;sum&eacute;. The left side explains the project as a playful mix of AI, design, and storytelling, with a list of example questions and a button to download the CV as a PDF." class="wp-image-91762" srcset="https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=3584 3584w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=1536 1536w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=2048 2048w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=288 288w, https://github.blog/wp-content/uploads/2025/10/quiviva.png?w=3000 3000w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1137.  
  1138.  
  1139.  
  1140. <p><a href="https://github.com/katawiecz/quiviva">Quiviva</a> by @katawiecz is an interactive AI-powered CV that turns a job hunt into a chat adventure. Ask about skills or projects, or type &ldquo;Gandalf&rdquo; to unlock secret nerd mode. All this goes to show that even r&eacute;sum&eacute;s can be fun.</p>
  1141.  
  1142.  
  1143.  
  1144. <h2 class="wp-block-heading" id="%f0%9f%95%b9%ef%b8%8f-game-on">&#128377;&#65039; Game on</h2>
  1145.  
  1146.  
  1147.  
  1148. <h3 class="wp-block-heading" id="ai-dventure-infinite-worlds-infinite-choices">AI-Dventure: Infinite worlds, infinite choices</h3>
  1149.  
  1150.  
  1151.  
  1152. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" width="1009" height="672" src="https://github.blog/wp-content/uploads/2025/10/ai-dventure.png?w=1009&#038;resize=1009%2C672" alt="A screenshot of a text adventure game." class="wp-image-91761" srcset="https://github.blog/wp-content/uploads/2025/10/ai-dventure.png?w=1009 1009w, https://github.blog/wp-content/uploads/2025/10/ai-dventure.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/ai-dventure.png?w=768 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1153.  
  1154.  
  1155.  
  1156. <p><a href="https://github.com/FedeCarollo/ai_dventure">AI-Dventure</a> by @FedeCarollo is an interactive text adventure built in Rust and powered by OpenAI&rsquo;s models. Players explore dynamically generated worlds in fantasy, horror, sci-fi, or historical settings where every command shapes the story and no two runs are the same.</p>
  1157.  
  1158.  
  1159.  
  1160. <h3 class="wp-block-heading" id="h-beatbugging-debug-to-the-beat">BeatBugging: Debug to the beat</h3>
  1161.  
  1162.  
  1163.  
  1164. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" width="759" height="437" src="https://github.blog/wp-content/uploads/2025/10/beatbugging.png?w=759&#038;resize=759%2C437" alt="A retro-style terminal interface titled &ldquo;BEATBUGGING SYSTEM&rdquo; shows a progress bar at 25%, simulating the initialization of a &ldquo;musical debugging interface&rdquo; with audio frequencies, memory readouts, and ASCII symbols displayed on a dark screen." class="wp-image-91760" srcset="https://github.blog/wp-content/uploads/2025/10/beatbugging.png?w=759 759w, https://github.blog/wp-content/uploads/2025/10/beatbugging.png?w=300 300w" sizes="auto, (max-width: 759px) 100vw, 759px" /></figure>
  1165.  
  1166.  
  1167.  
  1168. <p><a href="https://github.com/sandra-aliaga/beatbugging">BeatBugging</a> by @sandra-aliaga, @Joshep-c, @RyanValdivia, and @tniia turns debugging into a rhythm game that converts your system logs into musical beats. Built in Python, it lets you fix bugs to the rhythm on a 5-by-5 grid and makes debugging sound unexpectedly good.</p>
  1169.  
  1170.  
  1171.  
  1172. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped the team figure out next steps when they got stuck, offering helpful hints that kept development moving.
  1173.  
  1174.  
  1175.  
  1176. <h3 class="wp-block-heading" id="mumind-a-multiplayer-battle-of-wits-and-vibes">MuMind: A multiplayer battle of wits and vibes</h3>
  1177.  
  1178.  
  1179.  
  1180. <p><a href="https://github.com/FontesHabana/MuMind">MuMind</a> by @FontesHabana is a web-based multiplayer version of the party game Herd Mentality, where players try to match the majority&rsquo;s answers to score points. Built with React, Tailwind CSS, and Framer Motion, it offers multilingual support, lively animations, and a smooth, responsive experience.</p>
  1181.  
  1182.  
  1183.  
  1184. <h2 class="wp-block-heading" id="%f0%9f%83%8f-everything-but-the-kitchen-sink">&#127183; Everything but the kitchen sink</h2>
  1185.  
  1186.  
  1187.  
  1188. <h3 class="wp-block-heading" id="gitfrag-defrag-your-contributions-graph">GitFrag: Defrag your contributions graph</h3>
  1189.  
  1190.  
  1191.  
  1192. <figure class="wp-block-video"><video autoplay controls loop muted src="https://github.blog/wp-content/uploads/2025/10/gitfrag.mp4"></video></figure>
  1193.  
  1194.  
  1195.  
  1196. <p>@chornonoh-vova built <a href="https://github.com/chornonoh-vova/gitfrag">GitFrag</a> to reorganize your contributions graph using classic sorting algorithms (bubble, merge, quick, and counting sort). Each is visualized with smooth progress animations, GitHub login, and dark mode support. There&rsquo;s also a<a href="https://www.chornonoh-vova.com/blog/gitfrag-challenge"> wonderful writeup of how the developer approached it</a>.</p>
  1197.  
  1198.  
  1199.  
  1200. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @chornonoh-vova structure their understanding of algorithms and add thoughtful details that made their visualization shine.
  1201.  
  1202.  
  1203.  
  1204. <h3 class="wp-block-heading" id="h-code-sensei-meditate-your-way-through-vs-code">Code Sensei: Meditate your way through VS Code</h3>
  1205.  
  1206.  
  1207.  
  1208. <p><a href="https://github.com/redhatsam09/code-sensei">Code Sensei</a> by @redhatsam09 turns your VS Code sessions into a zen pixel adventure where your focus fuels the fun. Type to walk, pause to hop&mdash;but stay away too long away and your sensei meets a dramatic, 8-bit demise.</p>
  1209.  
  1210.  
  1211.  
  1212. <figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
  1213. <iframe loading="lazy" title="Code Sensei" width="500" height="281" src="https://www.youtube.com/embed/MHrUYFEAnhU?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
  1214. </div></figure>
  1215.  
  1216.  
  1217.  
  1218. <h3 class="wp-block-heading" id="h-reviewer-karma-good-vibes-for-great-reviews">Reviewer Karma: Good vibes for great reviews</h3>
  1219.  
  1220.  
  1221.  
  1222. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="702" width="1024" src="https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?resize=1024%2C702" alt="A leaderboard titled &ldquo;Scoring System&rdquo; and &ldquo;Current Rankings&rdquo; shows how reviewers earn points for giving code reviews, using positive emojis, and writing constructive comments. The rankings table lists @alice in first place with 18 points, followed by @bob, @carol, @dave, and @eve." class="wp-image-91759" srcset="https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?w=1796 1796w, https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?w=300 300w, https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/reviewer-karma.png?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  1223.  
  1224.  
  1225.  
  1226. <p><a href="https://github.com/master-wayne7/reviewer-karma-action">Reviewer Karma</a> by @master-wayne7 keeps your pull requests peaceful by rewarding reviewers for good vibes and great feedback. Every emoji, comment, and code critique earns points on a live leaderboard that turns pull request reviews into a friendly competition.</p>
  1227.  
  1228.  
  1229.  
  1230. <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24"><path d="M23.922 16.992c-.861 1.495-5.859 5.023-11.922 5.023-6.063 0-11.061-3.528-11.922-5.023A.641.641 0 0 1 0 16.736v-2.869a.841.841 0 0 1 .053-.22c.372-.935 1.347-2.292 2.605-2.656.167-.429.414-1.055.644-1.517a10.195 10.195 0 0 1-.052-1.086c0-1.331.282-2.499 1.132-3.368.397-.406.89-.717 1.474-.952 1.399-1.136 3.392-2.093 6.122-2.093 2.731 0 4.767.957 6.166 2.093.584.235 1.077.546 1.474.952.85.869 1.132 2.037 1.132 3.368 0 .368-.014.733-.052 1.086.23.462.477 1.088.644 1.517 1.258.364 2.233 1.721 2.605 2.656a.832.832 0 0 1 .053.22v2.869a.641.641 0 0 1-.078.256ZM12.172 11h-.344a4.323 4.323 0 0 1-.355.508C10.703 12.455 9.555 13 7.965 13c-1.725 0-2.989-.359-3.782-1.259a2.005 2.005 0 0 1-.085-.104L4 11.741v6.585c1.435.779 4.514 2.179 8 2.179 3.486 0 6.565-1.4 8-2.179v-6.585l-.098-.104s-.033.045-.085.104c-.793.9-2.057 1.259-3.782 1.259-1.59 0-2.738-.545-3.508-1.492a4.323 4.323 0 0 1-.355-.508h-.016.016Zm.641-2.935c.136 1.057.403 1.913.878 2.497.442.544 1.134.938 2.344.938 1.573 0 2.292-.337 2.657-.751.384-.435.558-1.15.558-2.361 0-1.14-.243-1.847-.705-2.319-.477-.488-1.319-.862-2.824-1.025-1.487-.161-2.192.138-2.533.529-.269.307-.437.808-.438 1.578v.021c0 .265.021.562.063.893Zm-1.626 0c.042-.331.063-.628.063-.894v-.02c-.001-.77-.169-1.271-.438-1.578-.341-.391-1.046-.69-2.533-.529-1.505.163-2.347.537-2.824 1.025-.462.472-.705 1.179-.705 2.319 0 1.211.175 1.926.558 2.361.365.414 1.084.751 2.657.751 1.21 0 1.902-.394 2.344-.938.475-.584.742-1.44.878-2.497Z"></path><path d="M14.5 14.25a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Zm-5 0a1 1 0 0 1 1 1v2a1 1 0 0 1-2 0v-2a1 1 0 0 1 1-1Z"></path></svg> Copilot cameo: GitHub Copilot helped @master-wayne7 write efficient Go code for the GitHub API, structure logic for assigning karma points, and handle repetitive tasks like error checking and markdown generation. It kept the project flowing smoothly from start to finish.
  1231.  
  1232.  
  1233.  
  1234. <hr class="wp-block-separator has-alpha-channel-opacity">
  1235.  
  1236.  
  1237.  
  1238. <h2 class="wp-block-heading" id="these-projects-show-whats-possible-when-we-let-our-curiosity-take-center-stage">These projects show what&rsquo;s possible when we let our curiosity take center stage</h2>
  1239.  
  1240.  
  1241.  
  1242. <p>Remember these are hackathon projects. They might not be feature complete, there may be bugs, spaghetti code, and the occasional rogue program escaped from the Grid. But they are clear examples of what we can accomplish when we do something just for the love of it.</p>
  1243.  
  1244.  
  1245.  
  1246. <p>All of our category winners get 12 months of GitHub Copilot Pro+.</p>
  1247.  
  1248.  
  1249.  
  1250. <p>If <em>For the Love of Code</em> proved anything, it&rsquo;s that creativity and code thrive best together&mdash;especially with Copilot lending a hand.</p>
  1251.  
  1252.  
  1253.  
  1254. <h2 class="wp-block-heading" id="shoutout-to-the-makers">Shoutout to the makers</h2>
  1255.  
  1256.  
  1257.  
  1258. <p>Congratulations to all of our winners: @Anmol0201, @answeryt, @Awesome-XV, @chornonoh-vova, @cpstroum, @Critlist, @FedeCarollo, @FontesHabana, @heza-ru, @joshep-c, @katawiecz, @lepetitprince99, @master-wayne7, @omkardongre, @RyanValdivia, @ozh, @rawrnuck, @redhatsam09, @sandra-aliaga, @shirsakm, @SUNSET-Sejong-University, @tniia.</p>
  1259.  
  1260.  
  1261.  
  1262. <p>Massive thank you to our judges, which included a mix of GitHub Stars, Campus Experts, and GitHub Developer Relations friends: @Ba4bes, @colbyfayock, @j0ashm, @JuanGdev, @howard-lio, @luckyjoseph, @metzinaround, @Taiwrash, and @xavidop.</p>
  1263.  
  1264.  
  1265.  
  1266. <p>And thank you Copilot for your assistance!</p>
  1267.  
  1268.  
  1269.  
  1270. <p>Now back to work everyone! Playtime is over.</p>
  1271.  
  1272.  
  1273.  
  1274. <p>&#128156; If you enjoyed <em>For the Love of Code</em>, stay tuned&hellip; <a href="https://itch.io/jam/game-off-2025"><em>Game Off 2025</em></a> begins this November!</p>
  1275. </body></html>
  1276. <p>The post <a href="https://github.blog/open-source/from-karaoke-terminals-to-ai-resumes-the-winners-of-githubs-for-the-love-of-code-challenge/">From karaoke terminals to AI résumés: The winners of GitHub’s For the Love of Code challenge</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1277. ]]></content:encoded>
  1281. <post-id xmlns="com-wordpress:feed-additions:1">91749</post-id> </item>
  1282. <item>
  1283. <title>Top security researcher shares their bug bounty process</title>
  1284. <link>https://github.blog/security/top-security-researcher-shares-their-bug-bounty-process/</link>
  1286. <dc:creator><![CDATA[Shilpa Kumari]]></dc:creator>
  1287. <pubDate>Wed, 22 Oct 2025 16:00:00 +0000</pubDate>
  1288. <category><![CDATA[Application security]]></category>
  1289. <category><![CDATA[Security]]></category>
  1290. <category><![CDATA[Supply chain security]]></category>
  1291. <category><![CDATA[Vulnerability research]]></category>
  1292. <category><![CDATA[Web application security]]></category>
  1293. <category><![CDATA[bug bounty]]></category>
  1294. <category><![CDATA[cybersecurity]]></category>
  1295. <category><![CDATA[Cybersecurity Awareness Month]]></category>
  1296. <category><![CDATA[GitHub Security]]></category>
  1297. <guid isPermaLink="false">https://github.blog/?p=91734</guid>
  1298.  
  1299. <description><![CDATA[<p>For this year’s Cybersecurity Awareness Month, the GitHub Bug Bounty team is excited to put the spotlight on a talented security researcher—André Storfjord Kristiansen!</p>
  1300. <p>The post <a href="https://github.blog/security/top-security-researcher-shares-their-bug-bounty-process/">Top security researcher shares their bug bounty process</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1301. ]]></description>
  1302. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  1303. <html><body><p><em>As we wrap Cybersecurity Awareness Month, the GitHub Bug Bounty team is excited to spotlight another top performing security researcher who participates in the GitHub Security Bug Bounty Program, Andr&eacute; Storfjord Kristiansen!</em></p>
  1304.  
  1305.  
  1306.  
  1307. <p>GitHub is dedicated to maintaining the security and reliability of the code that powers millions of development projects every day. <a href="https://bounty.github.com/">GitHub&rsquo;s Bug Bounty Program</a> is a cornerstone of our commitment to securing both our platform and the broader software ecosystem.</p>
  1308.  
  1309.  
  1310.  
  1311. <p>With the rapid growth of AI-powered features like <a href="https://github.com/features/copilot">GitHub Copilot</a>, <a href="https://docs.github.com/en/copilot/concepts/agents/coding-agent/about-coding-agent">GitHub Copilot coding agent</a>, <a href="https://githubnext.com/projects/github-spark">GitHub Spark</a>, and more, our focus on security is stronger than ever&mdash;especially as we pioneer new ways to assist developers with intelligent coding. Collaboration with skilled security researchers remains essential, helping us identify and resolve vulnerabilities across both traditional and emerging technologies.</p>
  1312.  
  1313.  
  1314.  
  1315. <p>We have also been closely auditing the researchers participating in our public program&mdash;to identify those who consistently demonstrate expertise and impact&mdash;and inviting them to our exclusive VIP bounty program. VIP researchers get direct access to:</p>
  1316.  
  1317.  
  1318.  
  1319. <ul class="wp-block-list">
  1320. <li>Early previews of beta products and features before public launch</li>
  1321.  
  1322.  
  1323.  
  1324. <li>Dedicated engagement with GitHub Bug Bounty staff and the engineers behind the features they&rsquo;re testing &#128516;</li>
  1325.  
  1326.  
  1327.  
  1328. <li>Unique Hacktocat swag&mdash;including this year&rsquo;s brand new <a href="https://bugbounty.printengine.com/page/2/">collection</a>!</li>
  1329. </ul>
  1330.  
  1331.  
  1332.  
  1333. <p>Explore <a href="https://github.blog/security/vulnerability-research/githubs-revamped-vip-bug-bounty-program/#how-can-one-receive-an-invite">this blog post</a> to learn more about our VIP program and discover how you can <a href="https://bounty.github.com/#:~:text=How%20can%20I%20earn%20an%20invitation%20to%20the%20GitHub%20VIP%20program%3F">earn an invitation</a>!</p>
  1334.  
  1335.  
  1336.  
  1337. <p>As part of ongoing <a href="https://github.blog/security/vulnerability-research/kicking-off-cybersecurity-awareness-month-2025-researcher-spotlights-and-enhanced-incentives/">Cybersecurity Awareness Month celebration</a> this October, we&rsquo;re spotlighting another outstanding researcher from our Bug Bounty program and exploring their unique methodology, techniques, and experiences hacking on GitHub. <strong>@dev-bio</strong> is particularly skilled in identifying injection-related vulnerabilities and has discovered some of the most subtle and impactful issues in our ecosystem. They are also known for providing thorough, detailed reports that greatly assist with impact assessments and enable us to take quicker, more effective action.</p>
  1338.  
  1339.  
  1340.  
  1341. <hr class="wp-block-separator has-alpha-channel-opacity">
  1342.  
  1343.  
  1344.  
  1345. <p><strong>How did you get involved with Bug Bounty? What has kept you coming back to it?</strong></p>
  1346.  
  1347.  
  1348.  
  1349. <p>I got involved with the program quite coincidentally while working on a personal project in my spare time. Given my background in (and passion for) software engineering, I&rsquo;m always curious about how systems behave, especially when it comes to handling complex edge cases. That curiosity often leads me to pick apart new features or changes I encounter to see how they hold up&mdash;something that has taken me down fascinating rabbit holes and ultimately led to some findings with great impact.</p>
  1350.  
  1351.  
  1352.  
  1353. <p>What keeps me going is the thrill of showing how seemingly minor issues can have real-world impact. Taking something small and possibly overlooked, exploring its implications, and demonstrating how it could escalate into a serious vulnerability feels very rewarding.</p>
  1354.  
  1355.  
  1356.  
  1357. <p><strong>What do you enjoy doing when you aren&rsquo;t hacking?</strong></p>
  1358.  
  1359.  
  1360.  
  1361. <p>Having recently become a father of two, much of my time outside of work revolves around being present with my family and striving to be the best version of myself for them. I also want to acknowledge that my partner&mdash;my favorite person and better half&mdash;has been incredibly supportive. Even if she has no clue what I&rsquo;m doing during my late-night sessions, she gives me uninterrupted time to work on my side projects, for which I&rsquo;m deeply grateful.</p>
  1362.  
  1363.  
  1364.  
  1365. <p>I&rsquo;m from Norway, and one of the many benefits of living here is the easy access to incredible nature. We try to make the most of it together through hiking, camping, and cross-country skiing. Being out in the wilderness is a perfect way to disconnect, recharge, and gain perspective away from a busy world. We find that after time outdoors, one can come back more grounded, with a clear mind and renewed focus.</p>
  1366.  
  1367.  
  1368.  
  1369. <p><strong>How do you keep up with and learn about vulnerability trends?</strong></p>
  1370.  
  1371.  
  1372.  
  1373. <p>I stay up to date by reading write-ups from other researchers, which are an excellent way to see how others are approaching problems and what kinds of vulnerabilities are being uncovered. While this is important, one should also attempt to stay ahead of the curve, so I try to identify and dive into areas that are in need of further research.</p>
  1374.  
  1375.  
  1376.  
  1377. <p>Professionally, as a security engineer, my primary area of expertise is software supply chain security, an often-neglected but increasingly important field. I spend much of my time researching gaps and developing solutions to mitigate emerging threats. I&rsquo;m also very lucky to work closely with some of the best talent in Norway.</p>
  1378.  
  1379.  
  1380.  
  1381. <p><strong>What tools or workflows have been game-changers for your research? Are there any lesser-known utilities you recommend?</strong></p>
  1382.  
  1383.  
  1384.  
  1385. <p>When doing research in my spare time, I prefer to write my own tools rather than relying solely on what you get off the shelf, as I find that it gives me a deeper understanding of the problem and helps me identify new areas that could be worth exploring in the future.</p>
  1386.  
  1387.  
  1388.  
  1389. <p>None of my personal security tooling has been published yet, but I plan to&mdash;eventually&trade;&mdash;release a toolkit to build comprehensive offline graphs of GitHub organizations with an extensible query suite to quickly uncover common misconfigurations and hidden attack paths.</p>
  1390.  
  1391.  
  1392.  
  1393. <p><strong>What are your favorite classes of bugs to research and why?</strong></p>
  1394.  
  1395.  
  1396.  
  1397. <p>I&rsquo;m particularly drawn to injection-related vulnerabilities, subtle logical flaws, and overlooked assumptions that may not seem important at first glance. Recently, I&rsquo;ve been intrigued by novel techniques for bypassing even the strictest content security policies.</p>
  1398.  
  1399.  
  1400.  
  1401. <p>What I enjoy most is demonstrating how seemingly benign findings can be chained together into something with significant impact. These vulnerabilities often expose weaknesses in the underlying design rather than just surface-level issues. My passion for building resilient systems naturally shapes this approach, driving me to explore how small cracks can compromise a system&rsquo;s overall integrity.</p>
  1402.  
  1403.  
  1404.  
  1405. <p><strong>You&rsquo;ve found some complex and significant bugs in your work. Can you talk a bit about your process?</strong></p>
  1406.  
  1407.  
  1408.  
  1409. <p>The most significant discoveries I have made in my spare time have been coincidental and, in most cases, a side effect of being sidetracked by my own curiosity, rather than the result of a targeted approach with a rigid methodology.</p>
  1410.  
  1411.  
  1412.  
  1413. <p>I&rsquo;ve always had an insatiable curiosity and fascination with how systems work under the hood, and I let that curiosity guide my process outside of work. When I notice something unusual, I dig deeper, peeling back the layers until I fully understand what&rsquo;s happening. From there&mdash;if it&rsquo;s worthwhile&mdash;I carefully document each step to map out potential attack paths and piece together a clear, comprehensive picture of the vulnerability, which enables me to build a strong foundation for further analysis and reporting.</p>
  1414.  
  1415.  
  1416.  
  1417. <p><strong>Do you have any advice or recommended resources for researchers looking to get involved with Bug Bounty?</strong></p>
  1418.  
  1419.  
  1420.  
  1421. <p>Don&rsquo;t settle for a simple finding. Dig deeper and explore its implications. When you have a grasp of the bigger picture, seemingly benign issues could turn out to have substantial impact.</p>
  1422.  
  1423.  
  1424.  
  1425. <p><strong>Do you have any social media platforms you&rsquo;d like to share with our readers?</strong></p>
  1426.  
  1427.  
  1428.  
  1429. <p>Currently I have a <a href="https://pages.dev.bio/">page</a>, where I&rsquo;ll be posting interesting content in the near future. I&rsquo;m also on <a href="https://www.linkedin.com/in/storfjord">LinkedIn</a>.</p>
  1430.  
  1431.  
  1432.  
  1433. <hr class="wp-block-separator has-alpha-channel-opacity">
  1434.  
  1435.  
  1436.  
  1437. <p>Thank you, @dev-bio, for participating in GitHub&rsquo;s bug bounty researcher spotlight! Each submission to our bug bounty program is a chance to make GitHub, our products, and our customers more secure, and we continue to welcome and appreciate collaboration with the security research community. So, if this inspired you to go hunting for bugs, feel free to report your findings through <a href="https://www.hackerone.com/Github">HackerOne</a>.</p>
  1438. </body></html>
  1439. <p>The post <a href="https://github.blog/security/top-security-researcher-shares-their-bug-bounty-process/">Top security researcher shares their bug bounty process</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1440. ]]></content:encoded>
  1444. <post-id xmlns="com-wordpress:feed-additions:1">91734</post-id> </item>
  1445. <item>
  1446. <title>How to update community health files with AI</title>
  1447. <link>https://github.blog/ai-and-ml/github-copilot/how-to-update-community-health-files-with-ai/</link>
  1449. <dc:creator><![CDATA[Alexandra Lietzke]]></dc:creator>
  1450. <pubDate>Tue, 21 Oct 2025 16:00:00 +0000</pubDate>
  1451. <category><![CDATA[AI & ML]]></category>
  1452. <category><![CDATA[GitHub Copilot]]></category>
  1453. <category><![CDATA[community health files]]></category>
  1454. <category><![CDATA[maintainers]]></category>
  1455. <guid isPermaLink="false">https://github.blog/?p=91663</guid>
  1456.  
  1457. <description><![CDATA[<p>Have you ever thought about using AI to update community health files for your repositories? This blog shares actionable next steps for doing just that, including a starter kit with a checklist and tutorials on how to create three useful files.</p>
  1458. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/how-to-update-community-health-files-with-ai/">How to update community health files with AI</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1459. ]]></description>
  1460. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  1461. <html><body><p>Maintaining your project&rsquo;s community health files shouldn&rsquo;t get in the way of writing code. <a href="https://github.com/features/copilot">GitHub Copilot</a> can help you update and enhance your documentation, so you can stay focused on what really matters: working on the projects that excite you most.</p>
  1462.  
  1463.  
  1464.  
  1465. <p>In this blog, we&rsquo;ll touch on some of the most common community health files (focusing on <code>README</code>, contributor guides, and licenses) and why they&rsquo;re so important for maintainers, along with actionable steps you can take to add them to your projects. &#10024;</p>
  1466.  
  1467.  
  1468.  
  1469. <aside data-color-mode="light" data-dark-theme="dark" data-light-theme="light_dimmed" class="wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--2" style="border-top-width:4px">
  1470. <h2 class="wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5" id="h-what-is-github-copilot" style="margin-top:0">What is GitHub Copilot?</h2>
  1471.  
  1472.  
  1473.  
  1474. <p><a href="https://github.com/features/copilot">GitHub Copilot</a> has evolved from a smart autocomplete tool into a multi-model, agentic assistant that understands your entire codebase and can carry out cross-file refactors, run terminal commands, and even draft pull requests.</p>
  1475. </aside>
  1476.  
  1477.  
  1478.  
  1479. <h2 class="wp-block-heading" id="what-are-community-health-files-and-why-are-they-so-important">What are community health files and why are they so important?</h2>
  1480.  
  1481.  
  1482.  
  1483. <p><strong>Community health files</strong> are standardized documents that help maintain a welcoming, organized, and collaborative environment in <a href="https://github.blog/open-source/new-to-open-source-heres-everything-you-need-to-get-started/">open source projects</a>. These files communicate expectations, guide contributors, and support the overall health of a repository. They do <em>not</em> include technical documentation or code itself, but rather the scaffolding that supports healthy collaboration. You can typically find them in a repository&rsquo;s root directory or in a special <code>.github</code> folder (if they need to be applied across multiple repositories).</p>
  1484.  
  1485.  
  1486.  
  1487. <p>Keeping these files up-to-date should be considered <a href="https://opensource.guide/building-community/">a practical investment into your project&rsquo;s future and reputation</a>, as they&rsquo;re often the first touchpoint for new contributors, and their existence signals project maturity and maintainability. They not only improve transparency, consistency, and collaboration, but also help set the tone for how contributors and maintainers interact and engage productively.&nbsp;</p>
  1488.  
  1489.  
  1490.  
  1491. <p>If crucial community health files are missing or outdated, everyone feels the effects. Picture this: Your open source project starts gaining traction with new contributors. They want to help, but your repository doesn&rsquo;t have the right files, which leads to contributors unintentionally formatting pull requests incorrectly, opening vague issues, and even introducing security vulnerabilities&mdash;all because they didn&rsquo;t know the proper procedures from the start. Now, your maintainers are overwhelmed and faced with answering the same questions over and over, while also trying to retroactively enforce standards.</p>
  1492.  
  1493.  
  1494.  
  1495. <p>It&rsquo;s clear that the presence of these files helps promote efficiency and clearly communicates best practices, which in turn, creates a better environment for contributors and makes life easier for maintainers&mdash;and thanks to AI, the process doesn&rsquo;t have to be manual. AI tools like GitHub Copilot, for example, can automatically detect missing or stale files, suggest updates, and even generate drafts&mdash;saving time and reducing human error.&nbsp;</p>
  1496.  
  1497.  
  1498.  
  1499. <p>Here are three common types of community health files and why they&rsquo;re so important for building a welcoming community (and don&rsquo;t worry, we&rsquo;ll tell you exactly how you can generate your own with Copilot later in this blog!):&nbsp;</p>
  1500.  
  1501.  
  1502.  
  1503. <p><strong>README</strong><br>Often one of the first things a visitor sees when viewing a repository, a<strong> </strong><a href="http://readme.md"><strong><code>README.MD</code></strong></a><strong> </strong>introduces the project and explains its purpose, along with how to get started. Intended to help remove barriers, this document gives your users crucial information they need to quickly get up and running&mdash;like what the project is, information on its features, and how to install or use it.&nbsp;</p>
  1504.  
  1505.  
  1506.  
  1507. <p><strong>CONTRIBUTOR GUIDE</strong><strong><br></strong>A <strong>contributor guide</strong> provides guidelines on how contributors can and should participate&mdash;things like coding standards and pull request instructions. This guide tells users how they can efficiently contribute and what to expect. For instance, does the project even accept contributions? Contributor guides help set standards and expectations.</p>
  1508.  
  1509.  
  1510.  
  1511. <p><strong>LICENSE</strong><strong><br></strong>A <strong>license </strong>specifies the legal terms under which the project can be used, modified, and distributed. In short, it tells people how they can use your software. A common example of this type of file is the MIT License.&nbsp;</p>
  1512.  
  1513.  
  1514.  
  1515. <aside data-color-mode="light" data-dark-theme="dark" data-light-theme="light_dimmed" class="wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--3" style="border-top-width:4px">
  1516. <h2 class="wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5" id="h-choosing-the-right-kind-of-license-for-your-project" style="margin-top:0">Choosing the right kind of license for your project</h2>
  1517.  
  1518.  
  1519.  
  1520. <p>While you are not required to choose a license for your repository, if you don&rsquo;t add one, others do not have permission to use, modify, or distribute your code. If you want your repository to be recognized as Open Source, according to the <a href="https://opensource.org/">Open Source Initiative</a> (OSI) and its definition, you should select a widely used OSI-approved <a href="https://opensource.org/licenses">Open Source License</a>.</p>
  1521.  
  1522.  
  1523.  
  1524. <p>Here are some resources on how to choose the right license and add it to your repository:&nbsp;</p>
  1525.  
  1526.  
  1527.  
  1528. <ul class="wp-block-list">
  1529. <li><a href="https://choosealicense.com/">How to choose an open source license</a></li>
  1530.  
  1531.  
  1532.  
  1533. <li><a href="https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project">The Legal Side of Open Source</a></li>
  1534.  
  1535.  
  1536.  
  1537. <li><a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository">Licensing a repository</a></li>
  1538.  
  1539.  
  1540.  
  1541. <li><a href="https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository">Adding a license to a repository</a></li>
  1542. </ul>
  1543. </aside>
  1544.  
  1545.  
  1546.  
  1547. <p>Here are some other popular <a href="https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file">community health files</a>:&nbsp;</p>
  1548.  
  1549.  
  1550.  
  1551. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>ISSUE/PULL REQUEST TEMPLATES</strong></td><td>Standardizes the format and information required when submitting issues or pull requests.</td></tr><tr><td><strong>SECURITY</strong></td><td>Provides instructions for reporting vulnerabilities and outlines the project&rsquo;s security policy.</td></tr><tr><td><strong>GOVERNANCE</strong></td><td>Explains how the project is managed, including roles, responsibilities, and decision-making processes.</td></tr><tr><td><strong>CODE OF CONDUCT</strong></td><td>Defines standards for how to engage in a community.</td></tr><tr><td><strong>SUPPORT</strong></td><td>Shares specific guidance on how others can get help with your project.</td></tr><tr><td><strong>FUNDING</strong></td><td>Displays a sponsor button in your repository to increase the visibility of funding options for your open source project.</td></tr></tbody></table></figure>
  1552.  
  1553.  
  1554.  
  1555. <p>And while it&rsquo;s not exactly considered a community health file, we wanted to give an honorable mention to&hellip; the <a href="https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions"><strong>Copilot instructions file</strong></a>, which is an AI configuration that complements health docs. It uses the other community health files as context and tells GitHub Copilot exactly how to interact with the codebase, including what to prioritize or avoid. This file helps ground the LLM&mdash;whether you&rsquo;re using GitHub Copilot or another LLM in VS Code, on <a href="https://github.com">github.com</a>, or Copilot coding agent&mdash;giving it an understanding of what your project is and how it&rsquo;s structured, allowing for consistency across your codebase.&nbsp;</p>
  1556.  
  1557.  
  1558.  
  1559. <p>Having these kinds of files in your project is so important, especially when it comes to scaling open source projects where maintainers probably don&rsquo;t have time to personally help every contributor.<br><br>That&rsquo;s where time-saving tools like GitHub Copilot come in handy. Keep on reading for actionable next steps, tips, and tutorials on the most efficient ways to add these files to your repositories. &#10024;</p>
  1560.  
  1561.  
  1562.  
  1563. <h2 class="wp-block-heading" id="starter-kit-how-to-update-community-health-files-using-github-copilot">Starter kit: How to update community health files using GitHub Copilot</h2>
  1564.  
  1565.  
  1566.  
  1567. <p>We created a starter kit for you that explains how you can use AI to add these valuable files to your projects, complete with prompting best practices, a checklist full of things to consider, and step-by-step tutorials on how to add three common files to your repository using Copilot. Let&rsquo;s dive in.&nbsp;</p>
  1568.  
  1569.  
  1570.  
  1571. <h3 class="wp-block-heading" id="h-part-one-prompting">Part one: Prompting</h3>
  1572.  
  1573.  
  1574.  
  1575. <p>Whether you&rsquo;re starting from scratch or refining existing documentation, GitHub Copilot can help you write clearer, more consistent community health files with just a few prompts.&nbsp;</p>
  1576.  
  1577.  
  1578.  
  1579. <p>One thing to note: The LLMs powering GitHub Copilot are nondeterministic, which means that you can receive different outputs each time you prompt the model. <a href="https://github.blog/ai-and-ml/generative-ai/prompt-engineering-guide-generative-ai-llms/">Prompt engineering</a> can drastically improve the quality and relevance of the outputs you get from an LLM, but you&rsquo;ll still want to verify the accuracy of these outputs, especially when using Copilot to generate more sensitive files like licenses that have legal weight.&nbsp;&nbsp;</p>
  1580.  
  1581.  
  1582.  
  1583. <aside data-color-mode="light" data-dark-theme="dark" data-light-theme="light_dimmed" class="wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--4" style="border-top-width:4px">
  1584. <h3 class="wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5" id="h-prompting-best-practices" style="margin-top:0">Prompting best practices</h3>
  1585.  
  1586.  
  1587.  
  1588. <p>Want better suggestions from Copilot when generating community health files? Try these tips when writing your prompts:</p>
  1589.  
  1590.  
  1591.  
  1592. <ul class="wp-block-list">
  1593. <li>Write clear, structured prompts, like &ldquo;Generate a <code>CONTRIBUTING.md</code> file for a <code>Node.js</code> project that includes setup instructions, coding standards, and pull request guidelines.&rdquo;</li>
  1594.  
  1595.  
  1596.  
  1597. <li>For an even better prompt, make sure you include important context like audience type, project goals, and tone.</li>
  1598.  
  1599.  
  1600.  
  1601. <li>Use <a href="https://docs.github.com/en/copilot/tutorials/customization-library/prompt-files/create-readme">existing prompt files</a> to help standardize requests.</li>
  1602. </ul>
  1603. </aside>
  1604.  
  1605.  
  1606.  
  1607. <h3 class="wp-block-heading" id="h-part-two-checklist">Part two: Checklist</h3>
  1608.  
  1609.  
  1610.  
  1611. <p>This checklist helps ensure that Copilot-generated content is accurate, inclusive, secure, and aligned with your project&rsquo;s goals.</p>
  1612.  
  1613.  
  1614.  
  1615. <h4 class="wp-block-heading" id="h-before-you-start">&#128269; Before you start</h4>
  1616.  
  1617.  
  1618.  
  1619. <ul class="wp-block-list">
  1620. <li>Have you reviewed existing community health files in similar or related repositories?</li>
  1621.  
  1622.  
  1623.  
  1624. <li>Do you have clear goals for what each file should communicate (e.g., onboarding, behavior expectations, security reporting)?</li>
  1625.  
  1626.  
  1627.  
  1628. <li>Are you familiar with your organization&rsquo;s GitHub usage policies and branding guidelines?</li>
  1629. </ul>
  1630.  
  1631.  
  1632.  
  1633. <h4 class="wp-block-heading" id="%f0%9f%a7%a0-prompting-copilot-effectively">&#129504; Prompting Copilot effectively</h4>
  1634.  
  1635.  
  1636.  
  1637. <ul class="wp-block-list">
  1638. <li>Are your prompts specific and contextual? (e.g., &ldquo;Generate a <code>CONTRIBUTING.md</code> for a Python-based open source project with a code style guide.&rdquo;)</li>
  1639.  
  1640.  
  1641.  
  1642. <li>Have you included examples or tone preferences in your prompt? (e.g., &ldquo;Use inclusive language and a welcoming tone.&rdquo;)</li>
  1643. </ul>
  1644.  
  1645.  
  1646.  
  1647. <h4 class="wp-block-heading" id="%f0%9f%9b%a1%ef%b8%8f-security-privacy">&#128737;&#65039; Security &amp; privacy</h4>
  1648.  
  1649.  
  1650.  
  1651. <ul class="wp-block-list">
  1652. <li>Are you avoiding prompts that include sensitive or proprietary information (e.g., internal credentials, private URLs, confidential project names)?</li>
  1653.  
  1654.  
  1655.  
  1656. <li>Have you reviewed your repository&rsquo;s visibility settings (public vs. private) and ensured that community health files are appropriate for that audience?</li>
  1657.  
  1658.  
  1659.  
  1660. <li>Are you familiar with GitHub Copilot&rsquo;s privacy settings and how your prompts and suggestions are handled?</li>
  1661.  
  1662.  
  1663.  
  1664. <li>Will your <code>SECURITY.md</code> include:
  1665. <ul class="wp-block-list">
  1666. <li>A clear contact method for reporting vulnerabilities?</li>
  1667.  
  1668.  
  1669.  
  1670. <li>A brief explanation of how security issues are triaged?</li>
  1671.  
  1672.  
  1673.  
  1674. <li>Any relevant links to your organization&rsquo;s responsible disclosure policy?</li>
  1675. </ul>
  1676. </li>
  1677. </ul>
  1678.  
  1679.  
  1680.  
  1681. <h4 class="wp-block-heading" id="%f0%9f%a7%be-reviewing-copilot-output">&#129534; Reviewing Copilot output</h4>
  1682.  
  1683.  
  1684.  
  1685. <ul class="wp-block-list">
  1686. <li>Does the generated content reflect your project&rsquo;s values and community standards?</li>
  1687.  
  1688.  
  1689.  
  1690. <li>Have you checked for hallucinated links, names, or policies that don&rsquo;t exist?</li>
  1691.  
  1692.  
  1693.  
  1694. <li>Are all references to external resources accurate and up-to-date?</li>
  1695. </ul>
  1696.  
  1697.  
  1698.  
  1699. <h4 class="wp-block-heading" id="%f0%9f%a7%aa-testing-feedback">&#129514; Testing &amp; feedback</h4>
  1700.  
  1701.  
  1702.  
  1703. <ul class="wp-block-list">
  1704. <li>Have you asked a teammate or contributor to review the generated files?</li>
  1705.  
  1706.  
  1707.  
  1708. <li>Have you tested any instructions (e.g., setup steps in <code>README</code> or <code>CONTRIBUTING</code>) to ensure they work?</li>
  1709.  
  1710.  
  1711.  
  1712. <li>Are you open to iterating based on community feedback?</li>
  1713. </ul>
  1714.  
  1715.  
  1716.  
  1717. <h3 class="wp-block-heading" id="h-part-three-tutorial">Part three: Tutorial</h3>
  1718.  
  1719.  
  1720.  
  1721. <p>In this tutorial, we&rsquo;ll walk through how you can use Copilot to quickly and easily update <code>README.md</code>, a <code>LICENSE</code> file, and <code>CONTRIBUTING.md</code>.</p>
  1722.  
  1723.  
  1724.  
  1725. <h4 class="wp-block-heading" id="%f0%9f%93%9d-create-a-readme">&#128221; Create a README&nbsp;</h4>
  1726.  
  1727.  
  1728.  
  1729. <p><strong>Why make a <code>README</code>? </strong>Adding a <code>README</code> provides a clear overview of your project, helping users and contributors quickly understand its purpose, setup, and usage. Without it, potential users could abandon your repository due to confusion or lack of context.</p>
  1730.  
  1731.  
  1732.  
  1733. <p>Here&rsquo;s how to make one:&nbsp;</p>
  1734.  
  1735.  
  1736.  
  1737. <ol class="wp-block-list">
  1738. <li><strong>Open GitHub Copilot Chat</strong> in your IDE (e.g., VS Code).</li>
  1739.  
  1740.  
  1741.  
  1742. <li><strong>Switch to agent mode</strong> to enable project-aware assistance.</li>
  1743.  
  1744.  
  1745.  
  1746. <li><strong>Select your preferred model</strong> (e.g., Claude for strong writing and coding support).</li>
  1747.  
  1748.  
  1749.  
  1750. <li><strong>Ensure your project is open</strong> in the IDE so Copilot can read its context (e.g., <code>package.json</code>, <code>app.tsx</code>).</li>
  1751.  
  1752.  
  1753.  
  1754. <li>In the chat window, type: &ldquo;Help me write a <code>README.md</code> for my project. Ensure it includes installation instructions, a project overview, and follows standard <code>README</code> practices.&rdquo;</li>
  1755.  
  1756.  
  1757.  
  1758. <li><strong>Review the generated README.md</strong>. Copilot will analyze your project files and generate a structured <code>README.md</code>.</li>
  1759.  
  1760.  
  1761.  
  1762. <li><strong>Validate the installation instructions manually</strong> to ensure accuracy (LLMs may <a href="https://github.blog/ai-and-ml/llms/demystifying-llms-how-they-can-do-things-they-werent-trained-to-do/#hallucinations">hallucinate)</a>.</li>
  1763.  
  1764.  
  1765.  
  1766. <li>If satisfied, <strong>click &ldquo;Keep&rdquo;</strong> to save the <code>README.md</code> file.</li>
  1767.  
  1768.  
  1769.  
  1770. <li><strong>Commit the <code>README.md</code></strong> to your repository.</li>
  1771. </ol>
  1772.  
  1773.  
  1774.  
  1775. <h4 class="wp-block-heading" id="%f0%9f%93%84-add-a-license">&#128196; Add a license</h4>
  1776.  
  1777.  
  1778.  
  1779. <p><strong>Why make a license? </strong>A license defines how others can legally use, modify, and distribute your code, protecting both your rights and theirs. It removes ambiguity and prevents misuse, making your project safer to adopt and contribute to.</p>
  1780.  
  1781.  
  1782.  
  1783. <p>Here&rsquo;s how to add one:&nbsp;</p>
  1784.  
  1785.  
  1786.  
  1787. <ol class="wp-block-list">
  1788. <li><strong>Open GitHub Copilot Chat</strong> in your IDE.</li>
  1789.  
  1790.  
  1791.  
  1792. <li>Decide <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository">what kind of license you want to add</a>.</li>
  1793.  
  1794.  
  1795.  
  1796. <li>Type the following prompt: &ldquo;Can you add [the license you want] to my project?&rdquo;</li>
  1797.  
  1798.  
  1799.  
  1800. <li>Copilot will generate a <code>LICENSE</code> file with the license of your choice.&nbsp;</li>
  1801.  
  1802.  
  1803.  
  1804. <li><strong>Review the license</strong> to ensure it&rsquo;s accurate (especially any copyright owner names and statements).</li>
  1805.  
  1806.  
  1807.  
  1808. <li>If correct, <strong>click &ldquo;Keep&rdquo;</strong> to save the file.</li>
  1809.  
  1810.  
  1811.  
  1812. <li><strong>Commit the <code>LICENSE</code> file</strong> to your repository.</li>
  1813. </ol>
  1814.  
  1815.  
  1816.  
  1817. <h4 class="wp-block-heading" id="%f0%9f%a4%9d-create-a-contributor-guide">&#129309;&nbsp; Create a contributor guide</h4>
  1818.  
  1819.  
  1820.  
  1821. <p><strong>Why make a contributor guide? </strong>A contributor guide streamlines collaboration by outlining contribution standards, workflows, and expectations. This makes it easier for others to get involved with your project. The goal is to reduce friction and errors while also encouraging consistent, scalable contributions.</p>
  1822.  
  1823.  
  1824.  
  1825. <p>Here&rsquo;s how to create one:&nbsp;</p>
  1826.  
  1827.  
  1828.  
  1829. <ol class="wp-block-list">
  1830. <li><strong>Open GitHub Copilot Chat</strong> in your IDE.</li>
  1831.  
  1832.  
  1833.  
  1834. <li>Click the <strong>&ldquo;+&rdquo; icon</strong> to start a new chat.</li>
  1835.  
  1836.  
  1837.  
  1838. <li>Type this prompt: <em>&ldquo;Create a contributing guide file that follows best practices and link it in the <code>README</code>.&rdquo;</em></li>
  1839.  
  1840.  
  1841.  
  1842. <li>Copilot will generate a <code>CONTRIBUTING.md</code> file with:
  1843. <ul class="wp-block-list">
  1844. <li>Contribution guidelines</li>
  1845.  
  1846.  
  1847.  
  1848. <li>Code standards</li>
  1849.  
  1850.  
  1851.  
  1852. <li>Pull request instructions</li>
  1853.  
  1854.  
  1855.  
  1856. <li>Issue reporting process</li>
  1857. </ul>
  1858. </li>
  1859.  
  1860.  
  1861.  
  1862. <li><strong>Review and edit</strong> the guide to match your team&rsquo;s workflow.</li>
  1863.  
  1864.  
  1865.  
  1866. <li><strong>Save and commit</strong> the <code>CONTRIBUTING.md</code> file.</li>
  1867.  
  1868.  
  1869.  
  1870. <li><strong>Update your README</strong> to include a link to the contributor guide:</li>
  1871. </ol>
  1872.  
  1873.  
  1874.  
  1875. <pre class="wp-block-code"><code>## Contributing
  1876. See <a href="https://m365.cloud.microsoft/CONTRIBUTING.md">CONTRIBUTING.md</a> for guidelines.</code></pre>
  1877.  
  1878.  
  1879.  
  1880. <h2 class="wp-block-heading" id="take-this-with-you">Take this with you</h2>
  1881.  
  1882.  
  1883.  
  1884. <p>GitHub Copilot isn&rsquo;t just for writing code&mdash;it can be your documentation sidekick, too. Helping you write smarter, faster, and with less friction, Copilot sharpens your community health files, scales best practices, and turns good intentions into great documentation.&nbsp;</p>
  1885.  
  1886.  
  1887.  
  1888. <p>The result? Better docs, stronger communities, and happier maintainers.</p>
  1889.  
  1890.  
  1891.  
  1892. <div class="wp-block-group post-content-cta has-global-padding is-layout-constrained wp-block-group-is-layout-constrained">
  1893. <p><a href="https://docs.github.com/en/copilot/about-github-copilot/github-copilot-features">Read the Docs</a> to learn more about GitHub Copilot features or <a href="https://resources.github.com/copilot-for-business/?ef_id=_k_Cj0KCQjwsp6pBhCfARIsAD3GZubTXuCGU1hy65GlbZ2fA1YjoRRhw64GoF8UI-lrQsnWSqAWJ7dC3QoaAqQ4EALw_wcB_k_&amp;OCID=AIDcmmc3fhtaow_SEM__k_Cj0KCQjwsp6pBhCfARIsAD3GZubTXuCGU1hy65GlbZ2fA1YjoRRhw64GoF8UI-lrQsnWSqAWJ7dC3QoaAqQ4EALw_wcB_k_&amp;gclid=Cj0KCQjwsp6pBhCfARIsAD3GZubTXuCGU1hy65GlbZ2fA1YjoRRhw64GoF8UI-lrQsnWSqAWJ7dC3QoaAqQ4EALw_wcB">get started</a> today.</p>
  1894. </div>
  1895. </body></html>
  1896. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/how-to-update-community-health-files-with-ai/">How to update community health files with AI</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1897. ]]></content:encoded>
  1901. <post-id xmlns="com-wordpress:feed-additions:1">91663</post-id> </item>
  1902. <item>
  1903. <title>Inside the breach that broke the internet: The untold story of Log4Shell</title>
  1904. <link>https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/</link>
  1906. <dc:creator><![CDATA[Gregg Cochran]]></dc:creator>
  1907. <pubDate>Mon, 20 Oct 2025 16:00:16 +0000</pubDate>
  1908. <category><![CDATA[Open Source]]></category>
  1909. <category><![CDATA[Log4j]]></category>
  1910. <category><![CDATA[open source]]></category>
  1911. <category><![CDATA[Security]]></category>
  1912. <guid isPermaLink="false">https://github.blog/?p=91594</guid>
  1913.  
  1914. <description><![CDATA[<p>Log4Shell proved that open source security isn't guaranteed and isn’t just a code problem. It's about supporting, enabling, and empowering the people behind the projects that build our digital infrastructure.</p>
  1915. <p>The post <a href="https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/">Inside the breach that broke the internet: The untold story of Log4Shell</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  1916. ]]></description>
  1917. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  1918. <html><body><p>When Christian Grobmeier went to help his son with a Minecraft problem, he found the game displaying a warning: &ldquo;We are suffering from a security hole from Log4J, please be careful and update immediately.&rdquo;</p>
  1919.  
  1920.  
  1921.  
  1922. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  1923. <p>I stared at the screen and told my son,<strong> &lsquo;I&rsquo;m sorry, it&rsquo;s my fault.&rsquo;</strong></p>
  1924. <cite>Christian Grobmeier, Log4j maintainer</cite></blockquote>
  1925.  
  1926.  
  1927.  
  1928. <p>This is the untold story of how one maintainer and the <a href="https://github.com/apache/logging-log4j2">Log4j</a> team navigated a crisis that exposed critical gaps in our digital infrastructure and demonstrated the importance of open source security and sustainability. Now, initiatives like the <a href="https://resources.github.com/github-secure-open-source-fund/">GitHub Secure Open Source Fund</a> are working to make sure it never happens again.</p>
  1929.  
  1930.  
  1931.  
  1932. <p>It all started a few hours earlier on a cold November day, when Christian, who is a maintainer of the open source project Log4j, planned to spend time playing games with his son. Instead, he found himself staring at his phone, watching notifications pile up in his inbox&mdash;10, then 20 emails flooding in. When he saw the words &ldquo;remote code execution,&rdquo; his first thought was: &ldquo;Maybe I&rsquo;m on the wrong mailing list.&rdquo;</p>
  1933.  
  1934.  
  1935.  
  1936. <p>He wasn&rsquo;t. And within hours, Christian would be at the center of what became known as Log4Shell: the most severe vulnerability in internet history, affecting billions of devices from Fortune 500 companies to Minecraft servers worldwide.</p>
  1937.  
  1938.  
  1939.  
  1940. <p>&ldquo;I told my son, I will play with you in like five minutes,&rdquo; Christian recalls. &ldquo;But he didn&rsquo;t see me for the next couple of days.&rdquo;</p>
  1941.  
  1942.  
  1943.  
  1944. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>Watch the full interview with Christian Grobmeier and Gregg Cochran, staff program manager at GitHub, above. &#128070;</strong></td></tr></tbody></table></figure>
  1945.  
  1946.  
  1947.  
  1948. <h2 class="wp-block-heading" id="h-the-ubiquity-that-made-log4shell-a-perfect-storm">The ubiquity that made Log4Shell a perfect storm</h2>
  1949.  
  1950.  
  1951.  
  1952. <p>Log4j is foundational software. This 20+ year-old Java logging library quietly powers system events in applications worldwide, like user logins and calculation results. But this small piece of software had quietly become a dependency in thousands of projects across the Java ecosystem.</p>
  1953.  
  1954.  
  1955.  
  1956. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  1957. <p>Log4j is such a small, tiny library. But everybody can use it in their software.</p>
  1958. <cite>Christian Grobmeier</cite></blockquote>
  1959.  
  1960.  
  1961.  
  1962. <p>That ubiquity made Log4Shell devastating. Financial services companies relied on it for compliance auditing. E-commerce systems used it to track security incidents. Insurance companies needed it to monitor their software behavior. In a 2022 Tidelift survey, 49% of open source developers reported that their organization relies on Java&mdash;and most of them were using Log4j without even knowing it.</p>
  1963.  
  1964.  
  1965.  
  1966. <p>When Christian realized the scope of the vulnerability, the weight hit him immediately: &ldquo;Literally all Java applications in the world could be affected. Even 10% would be a major problem. This would be catastrophic.&rdquo;</p>
  1967.  
  1968.  
  1969.  
  1970. <h2 class="wp-block-heading" id="h-a-vulnerability-that-scored-a-perfect-10">A vulnerability that scored a perfect 10</h2>
  1971.  
  1972.  
  1973.  
  1974. <p>Log4Shell reveals how a seemingly innocent feature became an attack vector. Log4j used <a href="https://docs.oracle.com/cd/E19747-01/819-0076/jndi.html">Java&rsquo;s Naming and Directory Interface</a> (JNDI) to provide flexibility, allowing developers to load software components from remote servers. But the library didn&rsquo;t validate whether JNDI lookup strings were coming from trusted sources.</p>
  1975.  
  1976.  
  1977.  
  1978. <p>&ldquo;How can a string break the internet?&rdquo; Christian asks.&nbsp;</p>
  1979.  
  1980.  
  1981.  
  1982. <p>The exploitation was frighteningly simple. An attacker could input a malicious JNDI string into any application field that gets logged&mdash;a username field, a search box, even a Minecraft chat message&mdash;and execute remote code on the target system.</p>
  1983.  
  1984.  
  1985.  
  1986. <pre class="wp-block-code language-plaintext"><code>jndi:&lt;protocol&gt;://&lt;server-name&gt;:&lt;port&gt;/&lt;path-to-object&gt;</code></pre>
  1987.  
  1988.  
  1989.  
  1990. <p>&ldquo;You don&rsquo;t even need to have special knowledge,&rdquo; Christian notes. &ldquo;You just run around and push the string wherever you want it.&rdquo;</p>
  1991.  
  1992.  
  1993.  
  1994. <p class="purple-text text-gradient-purple-coral" style="margin-top:var(--wp--preset--spacing--40);margin-bottom:var(--wp--preset--spacing--40)"><strong>The Common Vulnerability Scoring System (CVSS) gave Log4Shell a perfect 10: the highest possible score.</strong></p>
  1995.  
  1996.  
  1997.  
  1998. <p class="purple-text text-gradient-purple-coral" style="margin-top:var(--wp--preset--spacing--40);margin-bottom:var(--wp--preset--spacing--40)">&ldquo;The first time I heard about this score, I thought, maybe it&rsquo;s not so bad,&rdquo; Christian remembers. &ldquo;And then after a couple of days, I thought, yeah, <strong>maybe we should extend this to a score of 15 or 20.</strong>&ldquo;</p>
  1999.  
  2000.  
  2001.  
  2002. <h2 class="wp-block-heading" id="the-human-cost-of-maintaining-critical-infrastructure">The human cost of maintaining critical infrastructure</h2>
  2003.  
  2004.  
  2005.  
  2006. <p>The personal toll on maintainers during the Log4Shell crisis reveals the hidden human cost of our software supply chain. Christian and his team, mostly volunteers, suddenly found themselves responsible for patching a vulnerability affecting half the internet. The pressure was immense and deeply personal.</p>
  2007.  
  2008.  
  2009.  
  2010. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2011. <p>Some of us stopped sleeping. We all felt that either we fix it right now in the next few days, or we close this project.</p>
  2012. <cite>Christian Grobmeier</cite></blockquote>
  2013.  
  2014.  
  2015.  
  2016. <p>Fixing the initial vulnerability led to the discovery of additional issues, creating what Christian describes as &ldquo;a bag of water with a hole. When you patch the hole, you see another one.&rdquo;</p>
  2017.  
  2018.  
  2019.  
  2020. <p>Meanwhile, the community response was mixed. &ldquo;On the one hand, you have people who really hate you, and on the other hand, you have people who are really behind you,&rdquo; Christian explains.&nbsp;</p>
  2021.  
  2022.  
  2023.  
  2024. <p>Perhaps most telling:</p>
  2025.  
  2026.  
  2027.  
  2028. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2029. <p>Nobody stops in to check on you. They check on the project. There&rsquo;s also nobody standing up and saying, &lsquo;hey, thank you for the good work you&rsquo;re doing to remediate this issue.&rsquo;</p>
  2030. <cite>Christian Grobmeier</cite></blockquote>
  2031.  
  2032.  
  2033.  
  2034. <h2 class="wp-block-heading" id="how-the-github-secure-open-source-fund-is-strengthening-security">How the GitHub Secure Open Source Fund is strengthening security</h2>
  2035.  
  2036.  
  2037.  
  2038. <p>The Log4Shell incident highlighted a critical gap in open source security: Maintainers often lack the training and resources to build security into their projects from the ground up. This realization sparked initiatives like the GitHub Secure Open Source Fund, which provides both funding and security training to critical open source projects.</p>
  2039.  
  2040.  
  2041.  
  2042. <p>The fund has been effective and efficient as a form of proactive protection, pooled resources, and shared responsibility. Think of it as &ldquo;insurance&rdquo; for the open source supply chain&mdash;helping make the digital ecosystem safer and reducing risks that could impact billions of users.</p>
  2043.  
  2044.  
  2045.  
  2046. <p>Christian participated in the <a href="https://github.blog/open-source/maintainers/securing-the-supply-chain-at-scale-starting-with-71-important-open-source-projects/">GitHub Secure Open Source Fund</a> security training program, and the impact was transformative.</p>
  2047.  
  2048.  
  2049.  
  2050. <p>The training didn&rsquo;t just provide technical knowledge&mdash;it shifted his perspective. Christian explains, &ldquo;With this training, developers are no longer the weakest link. Instead, they&rsquo;re the first line of defense.&rdquo;</p>
  2051.  
  2052.  
  2053.  
  2054. <p>This change in mindset is crucial. As Christian puts it:</p>
  2055.  
  2056.  
  2057.  
  2058. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2059. <p>Ignorance is by far the worst and most critical security hole. It will basically break all software.</p>
  2060. <cite>Christian Grobmeier</cite></blockquote>
  2061.  
  2062.  
  2063.  
  2064. <p>When asked if the GitHub Secure Open Source Fund training could have prevented Log4Shell, Christian is direct: &ldquo;If this training had existed five years ago, maybe Log4Shell wouldn&rsquo;t be here today.&rdquo;</p>
  2065.  
  2066.  
  2067.  
  2068. <h2 class="wp-block-heading" id="technical-lessons-building-security-by-default">Technical lessons: Building security by default</h2>
  2069.  
  2070.  
  2071.  
  2072. <p>The Log4Shell incident taught the industry several critical lessons about secure development practices:</p>
  2073.  
  2074.  
  2075.  
  2076. <p><strong>1. Validate all external input</strong>: Never trust data that crosses trust boundaries, especially in foundational libraries that process user input.</p>
  2077.  
  2078.  
  2079.  
  2080. <p><strong>2. Disable dangerous features by default</strong>: Log4j now ships with JNDI lookups disabled by default.&nbsp;</p>
  2081.  
  2082.  
  2083.  
  2084. <p><strong>3. Implement defense in depth</strong>: Modern applications need multiple layers of protection, from input validation to runtime protections.</p>
  2085.  
  2086.  
  2087.  
  2088. <p><strong>4. Automate security scanning</strong>: Tools like GitHub&rsquo;s code scanning and Dependabot can catch vulnerabilities before they reach production.</p>
  2089.  
  2090.  
  2091.  
  2092. <p><strong>5. Maintain a software bills of materials (SBOMs)</strong>: When Log4Shell hit, many organizations couldn&rsquo;t determine if they were affected because they didn&rsquo;t know their dependencies.</p>
  2093.  
  2094.  
  2095.  
  2096. <p>&ldquo;I got phone calls from colleagues, asking me: &lsquo;Am I really affected?&rsquo; SBOMs give you a technical way to find out what dependencies you&rsquo;re using in a project,&rdquo; Christian explains.&nbsp;</p>
  2097.  
  2098.  
  2099.  
  2100. <h2 class="wp-block-heading" id="industry-wide-lessons-for-sustainable-open-source">Industry-wide lessons for sustainable open source</h2>
  2101.  
  2102.  
  2103.  
  2104. <p>While the technical lessons from Log4Shell are crucial, technology changes aren&rsquo;t enough. The deeper challenge lies in how we support the humans who maintain the open source infrastructure our world depends on. This crisis exposed several systemic issues in how we approach open source sustainability and security:</p>
  2105.  
  2106.  
  2107.  
  2108. <p><strong>Community is crucial</strong>: &ldquo;If you&rsquo;re maintaining open source software, just as one single person, that&rsquo;s a risk,&rdquo; Christian emphasizes.</p>
  2109.  
  2110.  
  2111.  
  2112. <p><strong>Security training needs to be accessible</strong>: Traditional security education often doesn&rsquo;t reach the maintainers who need it most.</p>
  2113.  
  2114.  
  2115.  
  2116. <p><strong>Funding alone isn&rsquo;t enough</strong>: While financial support helps, Christian found that training and community were equally important. When offered funding to pay team members, many declined due to tax implications or existing jobs.</p>
  2117.  
  2118.  
  2119.  
  2120. <p><strong>Kindness matters</strong>: &ldquo;Behind every small open source library, there&rsquo;s a human writing the code,&rdquo; Christian reminds us. &ldquo;If you find something that&rsquo;s not right, help out instead of being angry.&rdquo;</p>
  2121.  
  2122.  
  2123.  
  2124. <p><strong>Security can be improved for every project</strong>: During the program, Christian implemented multiple new security improvements, including hardening GitHub Actions against script injections, developing a new threat model, and collaborating with ScanCode to identify hidden Log4j artifacts in third-party code.</p>
  2125.  
  2126.  
  2127.  
  2128. <h2 class="wp-block-heading" id="your-role-in-securing-the-software-supply-chain">Your role in securing the software supply chain</h2>
  2129.  
  2130.  
  2131.  
  2132. <p>The Log4Shell story isn&rsquo;t just about one vulnerability; it&rsquo;s about the collective responsibility we all share in maintaining the open source ecosystem that powers the modern internet.</p>
  2133.  
  2134.  
  2135.  
  2136. <p><strong>For maintainers</strong>: Apply to programs like the <a href="https://resources.github.com/github-secure-open-source-fund/">GitHub Secure Open Source Fund</a>. <a href="http://gh.io/protect-your-project">Enable built-in security tools</a> like GitHub&rsquo;s <a href="https://docs.github.com/en/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning">code scanning</a> and <a href="https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide">Dependabot</a>. <a href="https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/exporting-a-software-bill-of-materials-for-your-repository">Export SBOMs</a> to help downstream users understand their dependencies, and <a href="https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/about-repository-security-advisories">publish security advisories</a> for all vulnerabilities found in your project.</p>
  2137.  
  2138.  
  2139.  
  2140. <p><strong>For enterprises: </strong>Become a Funding or Ecosystem Partner of the <a href="https://resources.github.com/github-secure-open-source-fund/">GitHub Secure Open Source Fund.</a> Invest engineering time in the upstream projects you depend on. Don&rsquo;t just consume open source&mdash;contribute with code, documentation, security reviews, and funding.</p>
  2141.  
  2142.  
  2143.  
  2144. <p><strong>For individual developers</strong>: Select carefully the new dependencies that you pull in, for example by <a href="https://scorecard.dev/">checking their security posture</a>. Consider the data you process may be attacker controlled and strictly validate untrusted inputs to prevent unintended behavior. Contribute test cases and documentation.</p>
  2145.  
  2146.  
  2147.  
  2148. <h2 class="wp-block-heading" id="the-path-forward">The path forward</h2>
  2149.  
  2150.  
  2151.  
  2152. <p>Today, <a href="https://github.com/apache/logging-log4j2">Log4j</a> has an 8.3 OpenSSF score, which demonstrates good security practices.</p>
  2153.  
  2154.  
  2155.  
  2156. <p>But the broader lesson extends beyond any single project. As Christian puts it:</p>
  2157.  
  2158.  
  2159.  
  2160. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2161. <p>Learning is the only cure for ignorance. So just keep learning.</p>
  2162. <cite>Christian Grobmeier</cite></blockquote>
  2163.  
  2164.  
  2165.  
  2166. <p>The Log4Shell incident showed us how quickly our digital world can be threatened by a single vulnerability. But it also demonstrated the power of the open source community to respond, adapt, and improve. The question isn&rsquo;t whether the next critical vulnerability will emerge&mdash;it&rsquo;s whether we&rsquo;ll be ready for it.</p>
  2167.  
  2168.  
  2169.  
  2170. <hr class="wp-block-separator has-alpha-channel-opacity">
  2171.  
  2172.  
  2173.  
  2174. <p><strong>Ready to strengthen your open source project&rsquo;s security?</strong> The GitHub Secure Open Source Fund provides funding, training, and resources to help maintainers build more secure software:</p>
  2175.  
  2176.  
  2177.  
  2178. <ul class="wp-block-list">
  2179. <li><strong>Projects and Maintainers:</strong> <a href="https://resources.github.com/github-secure-open-source-fund/">Apply now</a> to the GitHub Secure Open Source Fund and help make open source safer for everyone.</li>
  2180.  
  2181.  
  2182.  
  2183. <li><strong>Funding and Ecosystem Partners:</strong> <a href="https://docs.google.com/forms/d/e/1FAIpQLSeLMDmnxjbrneIPKlX8u3vK4I9ym6vRZPtWzMpT27apx6h9dw/viewform">Become a Funding or Ecosystem Partner</a> and support a more secure open source future. Join us on this mission to secure the software supply chain &mdash; at scale!</li>
  2184. </ul>
  2185.  
  2186.  
  2187.  
  2188. <hr class="wp-block-separator has-alpha-channel-opacity">
  2189.  
  2190.  
  2191.  
  2192. <h3 class="wp-block-heading" id="thank-you-to-all-of-our-partners">Thank you to all of our partners</h3>
  2193.  
  2194.  
  2195.  
  2196. <p>We couldn&rsquo;t do this without our incredible network of partners. Together, we are helping secure the open source ecosystem for everyone!&nbsp;</p>
  2197.  
  2198.  
  2199.  
  2200. <p><strong>Funding Partners: </strong>Alfred P. Sloan Foundation, American Express, Chainguard, Datadog, Herodevs, Kraken, Mayfield, Microsoft, Shopify, Stripe, Superbloom, Vercel, Zerodha, 1Password</p>
  2201.  
  2202.  
  2203.  
  2204. <p><strong>Ecosystem Partners: </strong>Ecosyste.ms, CURIOSS, Digital Data Design Institute Lab for Innovation Science, Digital Infrastructure Insights Fund, Microsoft for Startups, Mozilla, OpenForum Europe, Open Source Collective, OpenUK, Open Technology Fund, OpenSSF, Open Source Initiative, OpenJS Foundation, University of California, Santa Cruz OSPO, Sovereign Tech Agency, SustainOSS</p>
  2205. </body></html>
  2206. <p>The post <a href="https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/">Inside the breach that broke the internet: The untold story of Log4Shell</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2207. ]]></content:encoded>
  2211. <post-id xmlns="com-wordpress:feed-additions:1">91594</post-id> </item>
  2212. <item>
  2213. <title>Accelerate developer productivity with these 9 open source AI and MCP projects</title>
  2214. <link>https://github.blog/open-source/accelerate-developer-productivity-with-these-9-open-source-ai-and-mcp-projects/</link>
  2216. <dc:creator><![CDATA[Kevin Crosby]]></dc:creator>
  2217. <pubDate>Fri, 17 Oct 2025 16:00:00 +0000</pubDate>
  2218. <category><![CDATA[Open Source]]></category>
  2219. <category><![CDATA[generative AI]]></category>
  2220. <category><![CDATA[GitHub Copilot]]></category>
  2221. <category><![CDATA[LLM]]></category>
  2222. <category><![CDATA[machine learning]]></category>
  2223. <category><![CDATA[MCP]]></category>
  2224. <category><![CDATA[VS Code]]></category>
  2225. <guid isPermaLink="false">https://github.blog/?p=91591</guid>
  2226.  
  2227. <description><![CDATA[<p>GitHub Copilot and VS Code teams, along with the Microsoft Open Source Program Office (OSPO), sponsored these nine open source MCP projects that provide new frameworks, tools, and assistants to unlock AI-native workflows, agentic tooling, and innovation.</p>
  2228. <p>The post <a href="https://github.blog/open-source/accelerate-developer-productivity-with-these-9-open-source-ai-and-mcp-projects/">Accelerate developer productivity with these 9 open source AI and MCP projects</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2229. ]]></description>
  2230. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  2231. <html><body><p>With the emergence and rise of Model Context Protocol (MCP), developers are discovering revolutionary ways for AI and agents to interact with tools, codebases, and even browsers.&nbsp;&nbsp;</p>
  2232.  
  2233.  
  2234.  
  2235. <p>Building on top of the core technology, we are seeing projects, such as browser extensions and tools within code editors, enabling AI-native workflows and unlocking a new category of agentic tooling: innovative ecosystems and new projects focused on MCP-powered capabilities are changing the way we work.&nbsp;</p>
  2236.  
  2237.  
  2238.  
  2239. <p>In partnership with the Microsoft Open Source Program Office (OSPO), the GitHub Copilot and VS Code teams sponsored nine projects to accelerate innovation, security, and sustainability within open source. Below you&rsquo;ll find the projects and the three major themes we&rsquo;re seeing across their work.</p>
  2240.  
  2241.  
  2242.  
  2243. <h2 class="wp-block-heading" id="h-framework-and-platform-integrations-ecosystem-integrations-for-real-world-use-cases">Framework and platform integrations: Ecosystem integrations for real-world use cases &nbsp;</h2>
  2244.  
  2245.  
  2246.  
  2247. <p>These projects integrate <em>bring MCP capabilities into popular frameworks and ecosystems for AI-native tooling and help </em>MCP with widely used platforms, and enable agents to interact with real-world apps and workflows:&nbsp;</p>
  2248.  
  2249.  
  2250.  
  2251. <ul class="wp-block-list">
  2252. <li><a href="https://github.com/tadata-org/fastapi_mcp"><strong>fastapi_mcp</strong></a>: Expose secure FastAPI endpoints as MCP tools with minimal setup, authentication, and limited configuration&mdash;all with a unified infrastructure.&nbsp;</li>
  2253.  
  2254.  
  2255.  
  2256. <li><a href="https://github.com/antfu/nuxt-mcp"><strong>nuxt-mcp</strong></a>: Nuxt developer tools for route inspection and SSR debugging make it easier for your team to make models understand your Vite/Nuxt app better.&nbsp;</li>
  2257.  
  2258.  
  2259.  
  2260. <li><a href="https://github.com/CoplayDev/unity-mcp"><strong>unity-mcp</strong></a>: Unity MCP allows you to interface with game engine APIs for AI-assisted game development and gives your AI tools to manage assets, control scenes, edit scripts, and automate tasks within Unity&nbsp;</li>
  2261. </ul>
  2262.  
  2263.  
  2264.  
  2265. <h2 class="wp-block-heading" id="h-developer-experience-and-ai-enhanced-coding-ai-first-developer-productivity">Developer experience and AI-enhanced coding: AI-first developer productivity &nbsp;</h2>
  2266.  
  2267.  
  2268.  
  2269. <p>These projects empower AI,&nbsp; LLMs and agents to act as intelligent IDE assistants and code editors by improving developer workflows, semantic code understanding, and safe code execution.</p>
  2270.  
  2271.  
  2272.  
  2273. <ul class="wp-block-list">
  2274. <li><a href="https://github.com/upstash/context7"><strong>context7</strong></a>: Context7 pulls up-to-date, version-specific documentation and code examples straight from your code and plugs them directly into your AI and LLM prompts LLM&rsquo;s context.&nbsp;&nbsp;</li>
  2275.  
  2276.  
  2277.  
  2278. <li><a href="https://github.com/oraios/serena"><strong>serena</strong></a>: Semantic code editing and retrieval for agent-driven coding agent toolkit providing semantic retrieval and editing capabilities.&nbsp;&nbsp;</li>
  2279.  
  2280.  
  2281.  
  2282. <li><a href="https://github.com/steipete/Peekaboo"><strong>Peekaboo</strong></a>: Swift code analysis that turns what&rsquo;s on your screen into actionable AI context to create full GUI automation, and can be used for AI assistants.&nbsp;&nbsp;</li>
  2283.  
  2284.  
  2285.  
  2286. <li><a href="https://github.com/instavm/coderunner"><strong>coderunner</strong></a>: Coderunner turns LLMs into an instant, local execution partner that writes and runs code in a preconfigured sandbox on your machine, auto-installs tools, directly reads files, and returns outputs and generated artifacts.&nbsp;</li>
  2287. </ul>
  2288.  
  2289.  
  2290.  
  2291. <h2 class="wp-block-heading" id="h-automation-testing-and-orchestration-reliability-and-quality-assurance-for-mcp-infrastructure">Automation, testing and orchestration: Reliability and quality assurance for MCP infrastructure&nbsp;</h2>
  2292.  
  2293.  
  2294.  
  2295. <p>These projects help extend MCP infrastructure into production grade tools for automation pipelines and providing robust testing, and debugging tools. These help ensure you can run MCP at scale.&nbsp;</p>
  2296.  
  2297.  
  2298.  
  2299. <p>&nbsp;MCP server evaluation:&nbsp;</p>
  2300.  
  2301.  
  2302.  
  2303. <ul class="wp-block-list">
  2304. <li><a href="https://github.com/czlonkowski/n8n-mcp"><strong>n8n-mcp</strong></a>: n8n-MCP is an ultra-optimized platform that enhances n8n&rsquo;s workflow automation by streamlining workflow creation and orchestration. It integrates AI models to help users better understand and work with n8n nodes.</li>
  2305.  
  2306.  
  2307.  
  2308. <li><a href="https://github.com/MCPJam/inspector"><strong>inspector</strong></a>: A tool for testing and debugging MCP servers by inspecting protocol handshake, tools, resources, prompts, and OAuth flows. It offers a built-in LLM playground and lets you run eval simulations to catch security or performance regressions.&nbsp;&nbsp;</li>
  2309. </ul>
  2310.  
  2311.  
  2312.  
  2313. <h2 class="wp-block-heading" id="h-ai-workflows-and-agentic-developer-productivity-with-mcp-and-open-source">AI workflows and agentic developer productivity with MCP and open source&nbsp;</h2>
  2314.  
  2315.  
  2316.  
  2317. <p>Developers are building at incredible speed with the power of AI and MCP. These projects represent some of the fastest growing developer tools within the MCP ecosystem and community. They are tools that developers use and care about. GitHub Copilot and VS Code teams are excited to sponsor more open source projects that drive new innovations like MCP for agent-native development.&nbsp;</p>
  2318.  
  2319.  
  2320.  
  2321. <hr class="wp-block-separator has-alpha-channel-opacity">
  2322.  
  2323.  
  2324.  
  2325. <p>Sign up for<a href="https://github.com/sponsors?utm_source=github&amp;utm_medium=blog&amp;utm_campaign=FY226-Q1-MCP-SPONSORSHIPS"> GitHub Sponsors</a> today to join us in sponsoring these projects (and more!) and help support the<a href="https://modelcontextprotocol.io/"> MCP ecosystem</a>. You can also start exploring MCP with<a href="https://code.visualstudio.com/"> VS Code</a> and<a href="https://github.com/features/copilot?utm_source=github&amp;utm_medium=blog&amp;utm_campaign=FY226-Q1-MCP-SPONSORSHIPS"> GitHub Copilot</a> today!</p>
  2326. </body></html>
  2327. <p>The post <a href="https://github.blog/open-source/accelerate-developer-productivity-with-these-9-open-source-ai-and-mcp-projects/">Accelerate developer productivity with these 9 open source AI and MCP projects</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2328. ]]></content:encoded>
  2332. <post-id xmlns="com-wordpress:feed-additions:1">91591</post-id> </item>
  2333. <item>
  2334. <title>How to navigate GitHub Universe (or any tech conference) if you’re an introvert</title>
  2335. <link>https://github.blog/news-insights/company-news/how-to-navigate-github-universe-or-any-tech-conference-if-youre-an-introvert/</link>
  2337. <dc:creator><![CDATA[GitHub Staff]]></dc:creator>
  2338. <pubDate>Thu, 16 Oct 2025 16:14:02 +0000</pubDate>
  2339. <category><![CDATA[Company news]]></category>
  2340. <category><![CDATA[News & insights]]></category>
  2341. <category><![CDATA[GitHub Universe]]></category>
  2342. <guid isPermaLink="false">https://github.blog/?p=91588</guid>
  2343.  
  2344. <description><![CDATA[<p>If alone time is your love language—don’t worry, it’s ours too—you can still attend, learn from, and enjoy big events like GitHub Universe. Here are some practical tips on how.</p>
  2345. <p>The post <a href="https://github.blog/news-insights/company-news/how-to-navigate-github-universe-or-any-tech-conference-if-youre-an-introvert/">How to navigate GitHub Universe (or any tech conference) if you’re an introvert</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2346. ]]></description>
  2347. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  2348. <html><body><p>We know that the idea of big tech conferences can be overwhelming, especially if you&rsquo;re introverted, anxious, or are used to spending most of your day behind your computer. (Which is most of us.) And that&rsquo;s okay!&nbsp;</p>
  2349.  
  2350.  
  2351.  
  2352. <p>The good news is that GitHub Universe was designed for folks like you. This isn&rsquo;t just one long conference in a room with thousands of people and no exit. Universe offers all sorts of opportunities to take breaks, hang in small groups, or watch virtually, so that you can learn and network at whatever pace works for you. We&rsquo;ve built in events to make the experience extra comfortable, safe, and exciting for all.</p>
  2353.  
  2354.  
  2355.  
  2356. <p>[<a href="https://githubuniverse.com/?utm_source=Blog&amp;utm_medium=GitHub&amp;utm_campaign=tech_conference_introvert">Get your IRL pass</a>]</p>
  2357.  
  2358.  
  2359.  
  2360. <p>If you&rsquo;ve already got your pass but are feeling a bit shaky on how it&rsquo;ll all go, here are some practical tips for how to navigate tech conferences, like GitHub Universe.</p>
  2361.  
  2362.  
  2363.  
  2364. <h2 class="wp-block-heading" id="h-1-attend-smaller-sessions-or-workshops">1. Attend smaller sessions or workshops</h2>
  2365.  
  2366.  
  2367.  
  2368. <p>Instead of signing up for the largest, busiest sessions, go for the smaller workshops, niche panels, and breakout sessions. Small-group sessions often foster deeper connections and conversations, and they can help keep you from getting lost in the crowd.&nbsp;</p>
  2369.  
  2370.  
  2371.  
  2372. <p>This year&rsquo;s Universe will feature many <strong>interactive workshops</strong> (<a href="https://reg.githubuniverse.com/flow/github/universe25/attendee-portal/page/sessioncatalog?search.sessiontype=1681826483038003zyr1">explore the full list</a>), where the guest list will be small, and the conversations will be deep. You can also add demo-style<strong> sandbox sessions </strong>to your agenda, which include practical exercises, to keep your mind engaged!&nbsp;</p>
  2373.  
  2374.  
  2375.  
  2376. <p>You may also want to check out gatherings in our <strong>discussions lounge</strong>, where two to three facilitators will guide small groups through specific topics of interest, prioritizing active participation and collaboration.&nbsp;</p>
  2377.  
  2378.  
  2379.  
  2380. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image8.jpg?resize=1024%2C683" alt="Attendees working on laptops during conference session in presentation room." class="wp-image-91608" srcset="https://github.blog/wp-content/uploads/2025/10/image8.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image8.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image8.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image8.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image8.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2381.  
  2382.  
  2383.  
  2384. <h2 class="wp-block-heading" id="h-2-find-quiet-zones-and-recharge-spaces">2. Find quiet zones and recharge spaces</h2>
  2385.  
  2386.  
  2387.  
  2388. <p>We all know that introverts recharge alone. So if you need to step away and take some time to reflect, you should!</p>
  2389.  
  2390.  
  2391.  
  2392. <p>At Universe, we&rsquo;ve created <strong>dedicated lounges and recharge spaces</strong>, so you don&rsquo;t have to choose between skipping content and protecting your peace. Need a few minutes to unwind? We&rsquo;ll have a quiet room for phone-free decompression, meditation, and prayer. We&rsquo;ll also have plenty of drink options, snacks, and meals available if you need to keep your blood sugar up.</p>
  2393.  
  2394.  
  2395.  
  2396. <p>And don&rsquo;t forget to step outside and take in the stunning waterfront views at Fort Mason&mdash;a quick breath of ocean air can do wonders between sessions.</p>
  2397.  
  2398.  
  2399.  
  2400. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?resize=1024%2C683" alt="Sunset view across the bay with birds flying over water and hills in background." class="wp-image-91609" srcset="https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image7-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2401.  
  2402.  
  2403.  
  2404. <h2 class="wp-block-heading" id="h-3-join-curated-networking-activities">3. Join curated networking activities</h2>
  2405.  
  2406.  
  2407.  
  2408. <p>If large mixers without a planned topic of conversation feel daunting, you can look for guided or themed activities where the conversation already has a starting point.&nbsp;</p>
  2409.  
  2410.  
  2411.  
  2412. <p>At Universe, you can connect with people who share your passions at <a href="https://github.blog/news-insights/company-news/explore-the-best-of-github-universe-9-spaces-built-to-spark-creativity-connection-and-joy/">structured networking meetup spots</a>, including:&nbsp;</p>
  2413.  
  2414.  
  2415.  
  2416. <ul class="wp-block-list">
  2417. <li><strong>Recess!: </strong>Meet fellow attendees over your shared interests beyond the code. Whether you&rsquo;re a Lego enthusiast or a die-hard Swiftie, there&rsquo;s an opportunity for everyone to connect and simply have fun.</li>
  2418.  
  2419.  
  2420.  
  2421. <li><strong>Makerspace: </strong>Create interactive projects, from art to AI and music to robotics. Whether you build or just tinker, this is your playground.</li>
  2422.  
  2423.  
  2424.  
  2425. <li><strong>Open Source Zone: </strong>Connect with contributors and maintainers, explore open source projects, and celebrate the power of community-led software.&nbsp;</li>
  2426. </ul>
  2427.  
  2428.  
  2429.  
  2430. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?resize=1024%2C683" alt="Person at table assembling colorful LEGO buildings including a tower and house with organized brick containers." class="wp-image-91611" srcset="https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image3-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2431.  
  2432.  
  2433.  
  2434. <h2 class="wp-block-heading" id="h-4-set-personal-goals-and-boundaries">4. Set personal goals and boundaries</h2>
  2435.  
  2436.  
  2437.  
  2438. <p>Decide ahead of time what you want to get out of the event. Take a look at the agenda. What are your must-see sessions? Who are the people you want to meet? Build in plenty of breaks&mdash;without guilt!&nbsp;</p>
  2439.  
  2440.  
  2441.  
  2442. <p>Did you know that we offer a <strong>Universe agenda builder, curated schedules</strong>, and <strong><a href="https://github.blog/news-insights/company-news/github-universe-2025-heres-whats-in-store-at-this-years-developer-wonderland/#h-what-you-ll-experience">content tracks</a></strong>, so you can figure out the right sessions for your interests and goals? This makes it simple to stick to your plan (and pace yourself!).&nbsp;</p>
  2443.  
  2444.  
  2445.  
  2446. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?resize=1024%2C683" alt="Conference attendee in checkered blazer reading event map in crowded exhibition hall." class="wp-image-91612" srcset="https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image4-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2447.  
  2448.  
  2449.  
  2450. <h2 class="wp-block-heading" id="h-5-bring-a-conversation-starter">5. Bring a conversation starter</h2>
  2451.  
  2452.  
  2453.  
  2454. <p>Wearing a T-shirt, pin, or sticker related to your passions makes it easy for someone else to approach <em>you</em>. It may even give you the confidence to approach someone else, too.&nbsp;</p>
  2455.  
  2456.  
  2457.  
  2458. <p>Universe swag (and plenty of community stickers) are designed to help spark those natural, low-pressure conversations. And if you don&rsquo;t have any swag before the event, you can always visit <strong>The GitHub Shop</strong> and grab something day-of. We&rsquo;ll have a brand new GitHub Universe collection, so you&rsquo;ll be able to rep our latest and greatest.&nbsp;</p>
  2459.  
  2460.  
  2461.  
  2462. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?resize=1024%2C683" alt="Two attendees having conversation at tech conference, one wearing GitHub Star tag and blue cap." class="wp-image-91613" srcset="https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image6-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2463.  
  2464.  
  2465.  
  2466. <h2 class="wp-block-heading" id="h-6-take-it-online-with-livestream-or-on-demand-sessions">6. Take it online with livestream or on-demand sessions</h2>
  2467.  
  2468.  
  2469.  
  2470. <p>If attending in-person still doesn&rsquo;t feel right, don&rsquo;t forget that you can attend GitHub Universe virtually or catch keynotes and select session recordings later on-demand. Our goal: Make sure you can still participate and stay connected in a way that works best for you.&nbsp;</p>
  2471.  
  2472.  
  2473.  
  2474. <p>To note: This might not always be an option at other tech conferences or events, but it&rsquo;s always worth checking to see if there are ways to learn and connect from home if that&rsquo;s your preferred method.&nbsp;</p>
  2475.  
  2476.  
  2477.  
  2478. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?resize=1024%2C683" alt='Speaker presenting GitHub Models to large audience with "A new generation of AI engineers on GitHub" displayed on screen.' class="wp-image-91614" srcset="https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image5-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2479.  
  2480.  
  2481.  
  2482. <h2 class="wp-block-heading" id="h-conclusion">Conclusion</h2>
  2483.  
  2484.  
  2485.  
  2486. <p>We hope you see you at GitHub Universe this year. Don&rsquo;t forget that however you plan to attend&mdash;in-person, virtually, just a few workshops, or somewhere in between&mdash;it&rsquo;s all in your control. Whether you&rsquo;re introverted (like us) or extroverted, or somewhere in between, we hope you have the best time!&nbsp;</p>
  2487.  
  2488.  
  2489.  
  2490. <p>[<a href="https://githubuniverse.com/?utm_source=Blog&amp;utm_medium=GitHub&amp;utm_campaign=tech_conference_introvert">Register now</a>]</p>
  2491.  
  2492.  
  2493.  
  2494. <figure class="wp-block-image size-large"><img data-recalc-dims="1" loading="lazy" decoding="async" height="683" width="1024" src="https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?resize=1024%2C683" alt="View of Alcatraz Island through a colorful art installation frame with visitors silhouetted at waterfront." class="wp-image-91615" srcset="https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?w=1999 1999w, https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?w=300 300w, https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?w=768 768w, https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?w=1024 1024w, https://github.blog/wp-content/uploads/2025/10/image2-1.jpg?w=1536 1536w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2495. </body></html>
  2496. <p>The post <a href="https://github.blog/news-insights/company-news/how-to-navigate-github-universe-or-any-tech-conference-if-youre-an-introvert/">How to navigate GitHub Universe (or any tech conference) if you’re an introvert</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2497. ]]></content:encoded>
  2501. <post-id xmlns="com-wordpress:feed-additions:1">91588</post-id> </item>
  2502. <item>
  2503. <title>Copilot: Faster, smarter, and built for how you work now</title>
  2504. <link>https://github.blog/ai-and-ml/github-copilot/copilot-faster-smarter-and-built-for-how-you-work-now/</link>
  2506. <dc:creator><![CDATA[Ashley Willis]]></dc:creator>
  2507. <pubDate>Wed, 15 Oct 2025 15:00:00 +0000</pubDate>
  2508. <category><![CDATA[AI & ML]]></category>
  2509. <category><![CDATA[GitHub Copilot]]></category>
  2510. <category><![CDATA[GitHub Copilot CLI]]></category>
  2511. <category><![CDATA[LLM]]></category>
  2512. <category><![CDATA[MCP]]></category>
  2513. <guid isPermaLink="false">https://github.blog/?p=91555</guid>
  2514.  
  2515. <description><![CDATA[<p>Discover how GitHub Copilot has evolved from a high-powered autocomplete tool to a powerful, multi-model agentic assistant.</p>
  2516. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/copilot-faster-smarter-and-built-for-how-you-work-now/">Copilot: Faster, smarter, and built for how you work now</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2517. ]]></description>
  2518. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  2519. <html><body><p>You probably remember when <a href="https://github.com/features/copilot?utm_source=blog-generic-copilot-cta-oct-2025&amp;utm_campaign=copilot-generic-promotion-blog-launch-oct-2025">GitHub Copilot</a> first showed up in your editor with that little gray box. It was fast, surprising, and sometimes weird. But it hinted at something bigger: AI could actually <em>help</em> you code, not just autocomplete it.</p>
  2520.  
  2521.  
  2522.  
  2523. <p>Fast forward to today, and AI is part of our daily workflows. From Cursor to Windsurf and Claude Code to Gemini to OpenAI Codex, there&rsquo;s no shortage of new tools. And that&rsquo;s great. Developers need options.</p>
  2524.  
  2525.  
  2526.  
  2527. <p><strong>But with 20 million-plus developers across IDEs, the command line, and pull requests, GitHub Copilot is the most-used AI tool among developers</strong>, according to <a href="https://newsletter.pragmaticengineer.com/p/the-pragmatic-engineer-2025-survey">a recent Pragmatic Engineer survey</a>. Devs&nbsp;have used Copilot to accept more than 3 billion code suggestions to date. And every month, Copilot helps deliver millions of code reviews and contribute 1.2 million pull requests, directly inside GitHub.</p>
  2528.  
  2529.  
  2530.  
  2531. <p>And because GitHub is where your code already lives (plus your pull requests, reviews, and tests), Copilot doesn&rsquo;t stop at writing code. It plugs into everything you rely on via the GitHub MCP Server.</p>
  2532.  
  2533.  
  2534.  
  2535. <p>We haven&rsquo;t always been the fastest (though <a href="https://github.blog/changelog/?label=copilot">our Changelog may beg to differ</a>) or the loudest. But we&rsquo;ve been building Copilot since before ChatGPT existed, and we are focused on one purpose: to help developers turn TODOs into committed code. And while some chase the bleeding edge, we know developers don&rsquo;t want their production code balanced on it.&nbsp;</p>
  2536.  
  2537.  
  2538.  
  2539. <p>All that to say: if you tried Copilot early on, things have changed in some pretty big ways.&nbsp;</p>
  2540.  
  2541.  
  2542.  
  2543. <figure class="wp-block-image size-full"><img data-recalc-dims="1" loading="lazy" decoding="async" width="1232" height="2146" src="https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?resize=1232%2C2146" alt="A table showing how GitHub Copilot can help you code faster (Agent mode, Coding agent, Next edit suggestions, Latency improvements, Model choice, Copilot CLI), Build at scale (JetBrains + VS Code + CLI parity, Custom instructions, GitHub MCP Server, 20M+ developers), and Ship quality (Copilot Autofix, Code review, Improved model reasoning, Security that works, Built-in privacy)." class="wp-image-91570" srcset="https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=1232 1232w, https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=172 172w, https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=588 588w, https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=882 882w, https://github.blog/wp-content/uploads/2025/10/FeatureList_v6.png?w=1176 1176w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2544.  
  2545.  
  2546.  
  2547. <h2 class="wp-block-heading" id="h-from-autocomplete-to-actual-collaboration">From autocomplete to actual collaboration &#128187;</h2>
  2548.  
  2549.  
  2550.  
  2551. <p>If 2024 was about showing what&rsquo;s possible with AI, 2025 is about making it <em>practical</em>. Copilot has quietly grown from a neat autocomplete trick into a multi-modal, multi-model assistant that actually understands your projects and helps you move them forward.</p>
  2552.  
  2553.  
  2554.  
  2555. <p>After opening up support for multiple models from different providers in 2024,&nbsp; we&rsquo;ve been shipping new models almost as fast as they drop from OpenAI&rsquo;s latest releases to Google&rsquo;s Gemini 2.0 Flash.&nbsp;</p>
  2556.  
  2557.  
  2558.  
  2559. <p>This evolution didn&rsquo;t happen by accident. Developers told us what worked, what didn&rsquo;t, and that they wanted more powerful agentic workflows and multi-file editing. So we made that happen.&nbsp;</p>
  2560.  
  2561.  
  2562.  
  2563. <p>And that&rsquo;s just one part of how far Copilot&rsquo;s come. It&rsquo;s all part of a bigger goal: making Copilot smarter without you ever needing to install or configure a thing.&nbsp;</p>
  2564.  
  2565.  
  2566.  
  2567. <aside data-color-mode="light" data-dark-theme="dark" data-light-theme="light_dimmed" class="wp-block-group post-aside--large p-4 p-md-6 is-style-light-dimmed has-global-padding is-layout-constrained wp-block-group-is-layout-constrained is-style-light-dimmed--5" style="border-top-width:4px">
  2568. <h2 class="wp-block-heading h5-mktg gh-aside-title is-typography-preset-h5" id="h-built-into-the-platform-you-use-every-day" style="margin-top:0">Built into the platform you use every day</h2>
  2569.  
  2570.  
  2571.  
  2572. <p>Every AI vendor is racing to bolt their agentic tools into GitHub. That&rsquo;s because agents don&rsquo;t ship code in a vacuum. They plan tasks, open branches, run tests, and submit pull requests. And all of that already happens on GitHub where developers are collaborating on over 518 million projects.</p>
  2573.  
  2574.  
  2575.  
  2576. <p>Since Copilot lives inside the GitHub stack and has native support for GitHub MCP server, its agentic capabilities act on <em>real</em> repository context. It respects branch protections, works within your review cycles, and integrates directly with your CI/CD and security checks.</p>
  2577. </aside>
  2578.  
  2579.  
  2580.  
  2581. <h2 class="wp-block-heading" id="from-idea-to-merge-in-record-time-%e2%9a%a1">From idea to merge in record time &#9889;</h2>
  2582.  
  2583.  
  2584.  
  2585. <p>Over the last year, raw speed and agentic workflows helped define a new crop of AI tools. We took that as a challenge.</p>
  2586.  
  2587.  
  2588.  
  2589. <ul class="wp-block-list">
  2590. <li><a href="https://github.blog/ai-and-ml/github-copilot/agent-mode-101-all-about-github-copilots-powerful-mode/"><strong>Agent mode</strong></a><strong>:</strong> Copilot now takes on cross-file tasks, runs commands, refactors entire modules, and suggests terminal operations&mdash;all without leaving your editor.<br></li>
  2591.  
  2592.  
  2593.  
  2594. <li><a href="https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent"><strong>Coding agent</strong></a><strong>: </strong>Assign an issue to Copilot, and it drafts a pull request with code, tests, and context from your project. Coding agent now contributes to roughly 1.2 million pull requests per month.<br></li>
  2595.  
  2596.  
  2597.  
  2598. <li><a href="https://github.blog/changelog/2025-02-06-next-edit-suggestions-agent-mode-and-prompts-files-for-github-copilot-in-vs-code-january-release-v0-24/"><strong>Next-edit suggestions</strong></a><strong>:</strong> Copilot predicts the next change you&rsquo;ll make and offers it inline. One Tab and you&rsquo;re done.<br></li>
  2599.  
  2600.  
  2601.  
  2602. <li><strong>Low-latency completions:</strong> Most Copilot responses now render in under <strong>400 ms</strong> (fast enough that you stop noticing them).<br></li>
  2603.  
  2604.  
  2605.  
  2606. <li><a href="https://github.com/github/copilot-cli?utm_source=blog-cli-cta-oct-2025&amp;utm_campaign=copilot-generic-promotion-blog-launch-oct-2025"><strong>Copilot CLI</strong></a><strong>:</strong> The same brains, now in your terminal. Setup, debug, and script without switching windows.<br></li>
  2607.  
  2608.  
  2609.  
  2610. <li><a href="https://docs.github.com/en/copilot/reference/ai-models/model-comparison#recommended-models-by-task"><strong>Multi-model routing</strong></a><strong>:</strong> Different jobs call for different brains. Copilot gives you access to multiple LLMs from leading frontier AI firms.&nbsp;</li>
  2611. </ul>
  2612.  
  2613.  
  2614.  
  2615. <p>The result: fewer interruptions, faster loops, and a workflow that finally keeps pace with how you think.</p>
  2616.  
  2617.  
  2618.  
  2619. <h2 class="wp-block-heading" id="ai-that-scales-with-your-workflow-%f0%9f%93%90">AI that scales with your workflow &#128208;</h2>
  2620.  
  2621.  
  2622.  
  2623. <p>Copilot doesn&rsquo;t live in a new environment you need to learn. It&rsquo;s part of the same ecosystem you already use, and scales with it.&nbsp;</p>
  2624.  
  2625.  
  2626.  
  2627. <ul class="wp-block-list">
  2628. <li><a href="https://docs.github.com/en/copilot/get-started/features"><strong>JetBrains + VS Code + CLI parity</strong></a><strong>:</strong> Same Copilot, wherever you build.<br></li>
  2629.  
  2630.  
  2631.  
  2632. <li><a href="https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions"><strong>Custom instructions</strong></a><strong>:</strong> Drop a .copilot-instructions.md file in to teach Copilot your naming conventions, test frameworks, comment formats.<br></li>
  2633.  
  2634.  
  2635.  
  2636. <li><a href="https://github.com/github/github-mcp-server?utm_source=blog-mcp-server-cla-oct-2025&amp;utm_campaign=copilot-generic-promotion-blog-launch-oct-2025"><strong>GitHub MCP Server</strong></a><strong>:</strong> Lets any AI tool securely access your GitHub context (pull requests, issues, actions) without leaving GitHub.<br></li>
  2637.  
  2638.  
  2639.  
  2640. <li><a href="https://code.visualstudio.com/docs/copilot/customization/prompt-files"><strong>Workspace prompt files</strong></a><strong>:</strong> Reusable blueprints for consistent prompts across teams.<br></li>
  2641.  
  2642.  
  2643.  
  2644. <li><strong>20M+ developers strong:</strong> Every Copilot update compounds through the world&rsquo;s largest network of real developer data (and feedback).</li>
  2645. </ul>
  2646.  
  2647.  
  2648.  
  2649. <p>Copilot isn&rsquo;t a separate tool you &ldquo;add&rdquo; to GitHub. It&rsquo;s part of what makes GitHub a full-stack development platform. Other tools might help you code; Copilot helps you build, test, secure, and ship.</p>
  2650.  
  2651.  
  2652.  
  2653. <h2 class="wp-block-heading" id="smarter-cleaner-and-safer-code-%f0%9f%94%8d">Smarter, cleaner, and safer code &#128269;</h2>
  2654.  
  2655.  
  2656.  
  2657. <p>Fast is nice. Correct is better (ask us how we know). We&rsquo;ve spent a lot of cycles quietly leveling up Copilot&rsquo;s overall code quality and security guardrails where they matter most to you.&nbsp;</p>
  2658.  
  2659.  
  2660.  
  2661. <ul class="wp-block-list">
  2662. <li><a href="https://docs.github.com/en/code-security/code-scanning/managing-code-scanning-alerts/responsible-use-autofix-code-scanning"><strong>Copilot Autofix</strong></a><strong>: </strong>Detects and patches vulnerabilities automatically (it was used to fix over a million vulnerabilities this year alone).<br></li>
  2663.  
  2664.  
  2665.  
  2666. <li><a href="https://docs.github.com/en/copilot/how-tos/use-copilot-agents/request-a-code-review/use-code-review"><strong>Code review</strong></a><strong>: </strong>Summarizes diffs, flags logic bugs, and suggests fixes right inside your pull requests with a tool that powers millions of code reviews a month on GitHub.<br></li>
  2667.  
  2668.  
  2669.  
  2670. <li><strong>Improved model reasoning: </strong>Generates more readable, test-passing code with fewer lint errors and less regressions.<br></li>
  2671.  
  2672.  
  2673.  
  2674. <li><strong>CodeQL integration: </strong>Integrations with <a href="https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security">GitHub Advanced Security</a>, <a href="https://docs.github.com/en/copilot/tutorials/copilot-chat-cookbook/analyze-security/manage-dependency-updates">Dependabot</a>, and <a href="https://github.blog/ai-and-ml/github-copilot/from-chaos-to-clarity-using-github-copilot-agents-to-improve-developer-workflows/">GitHub Actions</a> keeps your supply chain solid.<br></li>
  2675.  
  2676.  
  2677.  
  2678. <li><a href="https://docs.github.com/en/copilot/how-tos/configure-content-exclusion"><strong>Built-in privacy</strong></a><strong>: </strong>Enterprise isolation, audit logs, and tenant-level control mean your work stays off the grid.&nbsp;</li>
  2679. </ul>
  2680.  
  2681.  
  2682.  
  2683. <p>Our research shows new code written with Copilot tends to have higher readability, better reliability, and improved maintainability scores.&nbsp;</p>
  2684.  
  2685.  
  2686.  
  2687. <p>Here&rsquo;s the good news: Copilot&rsquo;s backed by the same security stack that protects the world&rsquo;s largest open source ecosystem and more than 90% of Fortune 100 companies.</p>
  2688.  
  2689.  
  2690.  
  2691. <figure class="wp-block-image size-full"><img data-recalc-dims="1" loading="lazy" decoding="async" width="1232" height="2104" src="https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?resize=1232%2C2104" alt="A table demonstrating GitHub Copilot's leap forward from 2024 to 2025: Single model to Multi-model support, Single-file edits to Agent mode with multi-file reasoning, Basic completions to Next-edit suggestions and inline task automation, Chat in VS Code to IDE + JetBrains + CLI, Limited customization to Project-level instructions &amp; workspace prompts, Text only to Image, diagram, and UI inputs, Early security hints to Copilot Autofix &amp; deeper security integrations, and Competitive lag to 400ms responses &amp; GitHub MCP Server." class="wp-image-91572" srcset="https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=1232 1232w, https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=176 176w, https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=768 768w, https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=600 600w, https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=899 899w, https://github.blog/wp-content/uploads/2025/10/LeapForward_v5.png?w=1199 1199w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>
  2692.  
  2693.  
  2694.  
  2695. <h2 class="wp-block-heading" id="real-talk-copilot-vs-the-rest-%f0%9f%91%80">Real talk: Copilot vs. the rest &#128064;</h2>
  2696.  
  2697.  
  2698.  
  2699. <p>Let&rsquo;s be honest: there are some great tools out there that make agentic coding workflows feel intuitive and bring real polish to multi-file editing.&nbsp;</p>
  2700.  
  2701.  
  2702.  
  2703. <p>Copilot lives in GitHub. That means it&rsquo;s close to everything else you do, whether it&rsquo;s your pull requests, GitHub Actions workflows, or CI/CD pipelines. Every day, GitHub powers over <strong>3 million pull request merges</strong> and <strong>50 million actions runs</strong>. And Copilot lives in that flow.&nbsp;</p>
  2704.  
  2705.  
  2706.  
  2707. <p>Other tools might help you write code faster. But Copilot helps you ship better software.</p>
  2708.  
  2709.  
  2710.  
  2711. <p>That means:&nbsp;</p>
  2712.  
  2713.  
  2714.  
  2715. <ul class="wp-block-list">
  2716. <li><strong>No migration, no new IDE, no new habits: </strong>Copilot lives inside the tools you already use.&nbsp;</li>
  2717.  
  2718.  
  2719.  
  2720. <li><strong>Full-stack awareness: </strong>Your pull requests, reviews, tests, and workflows are part of the same conversation.&nbsp;</li>
  2721.  
  2722.  
  2723.  
  2724. <li><strong>End-to-end coverage: </strong>Copilot brings AI assistance to real-world delivery.&nbsp;</li>
  2725. </ul>
  2726.  
  2727.  
  2728.  
  2729. <h2 class="wp-block-heading" id="whats-next-%f0%9f%9a%80">What&rsquo;s next &#128640;</h2>
  2730.  
  2731.  
  2732.  
  2733. <p>We&rsquo;re just getting started.</p>
  2734.  
  2735.  
  2736.  
  2737. <p>At the end of this month, <strong>GitHub Universe 2025</strong> kicks off, and you can expect a <em>lot</em> of news. From smarter agent workflows to deeper multi-model integration and next-gen security features, we&rsquo;re building what&rsquo;s next for how software gets built.</p>
  2738.  
  2739.  
  2740.  
  2741. <p>Because our goal hasn&rsquo;t changed. We&rsquo;re here to help every developer commit code faster instead of chasing TODOs.&nbsp;</p>
  2742.  
  2743.  
  2744.  
  2745. <div class="wp-block-group post-content-cta has-global-padding is-layout-constrained wp-block-group-is-layout-constrained">
  2746. <p><strong>Ready to see how far we&rsquo;ve come?</strong> Get started with <a href="https://github.com/features/copilot?utm_source=blog-generic-copilot-cta-oct-2025&amp;utm_campaign=copilot-generic-promotion-blog-launch-oct-2025">GitHub Copilot</a> &gt;</p>
  2747. </div>
  2748. </body></html>
  2749. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/copilot-faster-smarter-and-built-for-how-you-work-now/">Copilot: Faster, smarter, and built for how you work now</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2750. ]]></content:encoded>
  2754. <post-id xmlns="com-wordpress:feed-additions:1">91555</post-id> </item>
  2755. <item>
  2756. <title>How GitHub Copilot and AI agents are saving legacy systems</title>
  2757. <link>https://github.blog/ai-and-ml/github-copilot/how-github-copilot-and-ai-agents-are-saving-legacy-systems/</link>
  2759. <dc:creator><![CDATA[Andrea Griffiths]]></dc:creator>
  2760. <pubDate>Tue, 14 Oct 2025 16:00:00 +0000</pubDate>
  2761. <category><![CDATA[AI & ML]]></category>
  2762. <category><![CDATA[GitHub Copilot]]></category>
  2763. <category><![CDATA[AI agents]]></category>
  2764. <category><![CDATA[COBOL]]></category>
  2765. <category><![CDATA[enterprise development]]></category>
  2766. <category><![CDATA[mainframe modernization]]></category>
  2767. <guid isPermaLink="false">https://github.blog/?p=91444</guid>
  2768.  
  2769. <description><![CDATA[<p>GitHub Copilot and AI agents are making legacy COBOL systems accessible to modern developers.</p>
  2770. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/how-github-copilot-and-ai-agents-are-saving-legacy-systems/">How GitHub Copilot and AI agents are saving legacy systems</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  2771. ]]></description>
  2772. <content:encoded><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
  2773. <html><body><p>Picture this: you&rsquo;re a developer in 2025, and your company just told you they need to modernize a mainframe system that processes millions of ATM transactions daily. We&rsquo;re talking about <a href="https://en.wikipedia.org/wiki/COBOL#">COBOL</a>, a programming language that&rsquo;s been around for 65 years. That&rsquo;s older than the internet.</p>
  2774.  
  2775.  
  2776.  
  2777. <p>Now, your first instinct might be to laugh or maybe cry a little. But here&rsquo;s the thing&mdash;COBOL isn&rsquo;t going anywhere. In fact, it&rsquo;s powering some of the largest and most critical systems on the planet right now.</p>
  2778.  
  2779.  
  2780.  
  2781. <p>The problem? <strong>Finding developers who understand COBOL is like finding unicorns.</strong> The original developers are retiring, and yet 200 billion lines of COBOL code are still running our banks, insurance companies, and government systems.</p>
  2782.  
  2783.  
  2784.  
  2785. <p>But here&rsquo;s the plot twist: we now have the opportunity to support the unicorns. We have GitHub Copilot and autonomous AI agents.</p>
  2786.  
  2787.  
  2788.  
  2789. <h2 class="wp-block-heading" id="h-meet-the-developer-who-s-modernizing-cobol-without-learning-cobol">Meet the developer who&rsquo;s modernizing COBOL (without learning COBOL)</h2>
  2790.  
  2791.  
  2792.  
  2793. <p>I recently spoke with <a href="https://www.linkedin.com/in/julia-kordick/">Julia Kordick</a>, Microsoft Global Black Belt, who&rsquo;s modernizing COBOL systems using AI. What&rsquo;s remarkable? She never learned COBOL.</p>
  2794.  
  2795.  
  2796.  
  2797. <p>Julia brought her AI expertise and worked directly with the people who had decades of domain knowledge. That partnership is the key insight here. She didn&rsquo;t need to become a COBOL expert. Instead, she focused on what she does best: designing intelligent solutions. The COBOL experts provided the legacy system knowledge.</p>
  2798.  
  2799.  
  2800.  
  2801. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2802. <p>When this whole idea of Gen AI appeared, we were thinking about how we can actually use AI to solve this problem that has not been really solved yet.</p>
  2803. <cite>Julia Kordick, Microsoft Global Black Belt</cite></blockquote>
  2804.  
  2805.  
  2806.  
  2807. <h2 class="wp-block-heading" id="h-the-three-step-framework-for-ai-powered-legacy-modernization">The three-step framework for AI-powered legacy modernization</h2>
  2808.  
  2809.  
  2810.  
  2811. <p>Julia and her team at Microsoft have cracked the code (pun intended) with a systematic approach that works for any legacy modernization project, not just COBOL. Here&rsquo;s their GitHub Copilot powered, battle-tested framework.</p>
  2812.  
  2813.  
  2814.  
  2815. <h3 class="wp-block-heading" id="h-step-1-code-preparation-reverse-engineering">Step 1: Code preparation (reverse engineering)</h3>
  2816.  
  2817.  
  2818.  
  2819. <p>The biggest problem with legacy systems? <strong>Organizations have no idea what their code actually does anymore.</strong> They use it, they depend on it, but understanding it? That&rsquo;s another story.</p>
  2820.  
  2821.  
  2822.  
  2823. <p>This is where GitHub Copilot becomes your archaeological tool. Instead of hiring consultants to spend months analyzing code, you can use AI to:</p>
  2824.  
  2825.  
  2826.  
  2827. <ul class="wp-block-list">
  2828. <li>Extract business logic from legacy files.</li>
  2829.  
  2830.  
  2831.  
  2832. <li>Document everything in markdown for human review.</li>
  2833.  
  2834.  
  2835.  
  2836. <li>Automatically identify call chains and dependencies.</li>
  2837.  
  2838.  
  2839.  
  2840. <li>Clean up irrelevant comments and historical logs.</li>
  2841.  
  2842.  
  2843.  
  2844. <li>Add additional information as comments where needed.</li>
  2845. </ul>
  2846.  
  2847.  
  2848.  
  2849. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>&#128161;<strong>Pro tip:</strong> Always have human experts review AI-generated analysis. AI is incredible at pattern recognition, but domain knowledge still matters for business context.</td></tr></tbody></table></figure>
  2850.  
  2851.  
  2852.  
  2853. <p>Here&rsquo;s what GitHub Copilot generates for you:&nbsp;</p>
  2854.  
  2855.  
  2856.  
  2857. <pre class="wp-block-code language-plaintext"><code># Business Logic Analysis Generated by GitHub Copilot
  2858. ## File Inventory
  2859. - listings.cobol: List management functionality (~100 lines)
  2860. - mainframe-example.cobol: Full mainframe program (~10K lines, high complexity)
  2861.  
  2862. ## Business Purpose
  2863. Customer account validation with balance checking
  2864. - Validates account numbers against master file
  2865. - Performs balance calculations with overdraft protection
  2866. - Generates transaction logs for audit compliance
  2867.  
  2868. ## Dependencies Discovered
  2869. - DB2 database connections via SQLCA
  2870. - External validation service calls
  2871. - Legacy print queue system</code></pre>
  2872.  
  2873.  
  2874.  
  2875. <h3 class="wp-block-heading" id="step-2-enrichment-making-code-ai-digestible">Step 2: Enrichment (making code AI-digestible)</h3>
  2876.  
  2877.  
  2878.  
  2879. <p>You usually need to add context to help AI understand your code better. Here&rsquo;s what that looks like:</p>
  2880.  
  2881.  
  2882.  
  2883. <p><strong>Translation:</strong> If your code has Danish, German, or other non-English comments, translate them. Models work better with English context.</p>
  2884.  
  2885.  
  2886.  
  2887. <p><strong>Structural analysis: </strong>COBOL has deterministic patterns. Even if you&rsquo;ve never written COBOL, you can leverage these patterns because they&rsquo;re predictable. Here&rsquo;s how:</p>
  2888.  
  2889.  
  2890.  
  2891. <p>COBOL programs always follow the same four-division structure:</p>
  2892.  
  2893.  
  2894.  
  2895. <ul class="wp-block-list">
  2896. <li>IDENTIFICATION DIVISION (metadata about the program)</li>
  2897.  
  2898.  
  2899.  
  2900. <li>ENVIRONMENT DIVISION (file and system configurations)</li>
  2901.  
  2902.  
  2903.  
  2904. <li>DATA DIVISION (variable declarations and data structures)</li>
  2905.  
  2906.  
  2907.  
  2908. <li>PROCEDURE DIVISION (the actual business logic)</li>
  2909. </ul>
  2910.  
  2911.  
  2912.  
  2913. <p>Ask GitHub Copilot to map these divisions for you. Use prompts like:</p>
  2914.  
  2915.  
  2916.  
  2917. <pre class="wp-block-code language-plaintext"><code>"Identify all the divisions in this COBOL file and summarize what each one does"
  2918.  
  2919. "List all data structures defined in the DATA DIVISION and their purpose"
  2920.  
  2921. "Extract the main business logic flow from the PROCEDURE DIVISION"</code></pre>
  2922.  
  2923.  
  2924.  
  2925. <p>The AI can parse these structured sections and explain them in plain English. You don&rsquo;t need to understand COBOL syntax. You just need to know that COBOL&rsquo;s rigid structure makes it easier for AI to analyze than more flexible languages.</p>
  2926.  
  2927.  
  2928.  
  2929. <p><strong>Documentation as source of truth:</strong> Save everything AI generates as markdown files that become the primary reference. Julia explained it this way: &ldquo;Everything that you let Copilot generate as a preparation, write it down as a markdown file so that it can actually reference these markdown files as source of truth.&rdquo;</p>
  2930.  
  2931.  
  2932.  
  2933. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>&#128161;Pro tip:</strong> COBOL&rsquo;s verbosity is actually an advantage here. Statements like <code>ADD TOTAL-SALES TO ANNUAL-REVENUE</code> are almost self-documenting. Ask Copilot to extract these business rules into natural language descriptions.</td></tr></tbody></table></figure>
  2934.  
  2935.  
  2936.  
  2937. <h3 class="wp-block-heading" id="step-3-automation-aids-scaling-the-process">Step 3: Automation Aids (Scaling the Process)</h3>
  2938.  
  2939.  
  2940.  
  2941. <p>Once you&rsquo;ve analyzed and enriched individual files, you need to understand how they all fit together. This is where you move from using Copilot interactively to building automated workflows with AI agents.</p>
  2942.  
  2943.  
  2944.  
  2945. <p>Julia&rsquo;s team built a framework using Microsoft Semantic Kernel, which orchestrates multiple specialized agents. Each agent has a specific job, and they work together to handle the complexity that would overwhelm a single AI call.</p>
  2946.  
  2947.  
  2948.  
  2949. <p>Here&rsquo;s what this orchestration looks like in practice:</p>
  2950.  
  2951.  
  2952.  
  2953. <ul class="wp-block-list">
  2954. <li><strong>Call chain mapping:</strong> Generate Mermaid diagrams showing how files interact. One agent reads your COBOL files, another traces the CALL statements between programs, and a third generates a visual diagram. You end up with a map of your entire system without manually tracing dependencies.</li>
  2955.  
  2956.  
  2957.  
  2958. <li><strong>Test-driven modernization:</strong> Extract business logic (agent 1), generate test cases that validate that logic (agent 2), then generate modern code that passes those tests (agent 3). The tests become your safety net during migration.</li>
  2959.  
  2960.  
  2961.  
  2962. <li><strong>Dependency optimization:</strong> Identify utility classes and libraries that you can replace with modern equivalents. An agent analyzes what third-party COBOL libraries you&rsquo;re using, checks if modern alternatives exist, and flags opportunities to simplify your migration.</li>
  2963. </ul>
  2964.  
  2965.  
  2966.  
  2967. <p>Think of it like this: Copilot in your IDE is a conversation. This framework is a production line. Each agent does one thing well, and the orchestration layer manages the workflow between them.</p>
  2968.  
  2969.  
  2970.  
  2971. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>&#128161;Pro tip:</strong> Use Mermaid diagrams to visualize complex dependencies before making any changes. It helps you catch edge cases early. You can generate these diagrams by asking Copilot to trace all CALL statements in your codebase and output them in Mermaid syntax. Mermaid chart example:</td></tr></tbody></table></figure>
  2972.  
  2973.  
  2974.  
  2975. <figure class="wp-block-image size-full"><img data-recalc-dims="1" loading="lazy" decoding="async" width="475" height="908" src="https://github.blog/wp-content/uploads/2025/10/mermaid.png?resize=475%2C908" alt="Flowchart showing the COBOL to Java modernization agent workflow. Seven boxes connected by arrows flow top to bottom: COBOLAnalyzerAgent, DependencyMapperAgent, Business Logic Extractor, Test Generator, JavaConverterAgent, Human Validation, and Production-Ready Java Quarkus Output." class="wp-image-91446" srcset="https://github.blog/wp-content/uploads/2025/10/mermaid.png?w=475 475w, https://github.blog/wp-content/uploads/2025/10/mermaid.png?w=157 157w" sizes="auto, (max-width: 475px) 100vw, 475px" /></figure>
  2976.  
  2977.  
  2978.  
  2979. <h2 class="wp-block-heading" id="h-the-reality-check-it-s-not-a-silver-bullet">The reality check: It&rsquo;s not a silver bullet</h2>
  2980.  
  2981.  
  2982.  
  2983. <p>Julia&rsquo;s brutally honest about limitations:</p>
  2984.  
  2985.  
  2986.  
  2987. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  2988. <p>Everyone who&rsquo;s currently promising you, &lsquo;hey, I can solve all your mainframe problems with just one click&rsquo; is lying to you.</p>
  2989. </blockquote>
  2990.  
  2991.  
  2992.  
  2993. <p>The reality is:</p>
  2994.  
  2995.  
  2996.  
  2997. <ul class="wp-block-list">
  2998. <li>Humans must stay in the loop for validation.</li>
  2999.  
  3000.  
  3001.  
  3002. <li>Each COBOL codebase is unique and complex.</li>
  3003.  
  3004.  
  3005.  
  3006. <li>We&rsquo;re early in the agentic AI journey.</li>
  3007.  
  3008.  
  3009.  
  3010. <li>Full automation is probably at least five years away.</li>
  3011. </ul>
  3012.  
  3013.  
  3014.  
  3015. <p>But that doesn&rsquo;t mean we can&rsquo;t make massive progress today.</p>
  3016.  
  3017.  
  3018.  
  3019. <h2 class="wp-block-heading" id="h-see-it-in-action-the-azure-samples-framework">See it in action: the Azure samples framework</h2>
  3020.  
  3021.  
  3022.  
  3023. <p>Julia and her team have open-sourced their entire framework. It&rsquo;s built with Microsoft Semantic Kernel for agentic orchestration and includes:</p>
  3024.  
  3025.  
  3026.  
  3027. <ul class="wp-block-list">
  3028. <li><strong>Multiple specialized agents:</strong> DependencyMapperAgent, COBOLAnalyzerAgent, JavaConverterAgent</li>
  3029.  
  3030.  
  3031.  
  3032. <li><strong>Cost tracking:</strong> See exactly how much each AI operation costs (usually $2-5 per 1000 lines analyzed)</li>
  3033.  
  3034.  
  3035.  
  3036. <li><strong>Human validation points:</strong> Built-in checkpoints for expert review</li>
  3037.  
  3038.  
  3039.  
  3040. <li><strong><code>doctor.sh</code>:</strong> A configuration and testing script that gets you started quickly</li>
  3041. </ul>
  3042.  
  3043.  
  3044.  
  3045. <p>Try running the COBOL modernization framework:</p>
  3046.  
  3047.  
  3048.  
  3049. <ol class="wp-block-list">
  3050. <li><strong>Fork the repository:</strong><a href="https://aka.ms/cobol"> aka.ms/cobol</a></li>
  3051.  
  3052.  
  3053.  
  3054. <li><strong>Set up your environment:</strong> Configure Azure OpenAI endpoint (or use local models for sensitive data)</li>
  3055.  
  3056.  
  3057.  
  3058. <li><strong>Run the doctor script:</strong> <code>./doctor.sh doctor</code> validates your setup and dependencies</li>
  3059.  
  3060.  
  3061.  
  3062. <li><strong>Start modernization:</strong> <code>./doctor.sh run</code> begins the automated process</li>
  3063. </ol>
  3064.  
  3065.  
  3066.  
  3067. <pre class="wp-block-code"><code># Quick setup for the impatient developer
  3068.  
  3069. git clone https://github.com/Azure-Samples/Legacy-Modernization-Agents
  3070.  
  3071. cd Legacy-Modernization-Agents
  3072.  
  3073. ./doctor.sh setup
  3074.  
  3075. ./doctor.sh run</code></pre>
  3076.  
  3077.  
  3078.  
  3079. <h2 class="wp-block-heading" id="the-business-case-that-changes-everything">The business case that changes everything</h2>
  3080.  
  3081.  
  3082.  
  3083. <p>This isn&rsquo;t just about technical debt. It&rsquo;s about business survival. Organizations are facing a critical shortage of COBOL expertise right when they need it most.</p>
  3084.  
  3085.  
  3086.  
  3087. <p>The traditional approach has been to hire expensive consultants, spend 5+ years on manual conversion, and end up with auto-generated code that&rsquo;s unmaintainable. I&rsquo;ve seen this play out at multiple organizations. The consultants come in, run automated conversion tools, hand over thousands of lines of generated code, and leave. Then the internal team is stuck maintaining code they don&rsquo;t understand in a language they&rsquo;re still learning.</p>
  3088.  
  3089.  
  3090.  
  3091. <p>The AI-powered approach changes this. You use AI to understand business logic, generate human-readable modern code, and maintain control of your intellectual property. Your team stays involved throughout the process. They learn the business logic as they go. The code that comes out the other end is something your developers can actually work with.</p>
  3092.  
  3093.  
  3094.  
  3095. <p>Julia explained the shift:</p>
  3096.  
  3097.  
  3098.  
  3099. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  3100. <p>What a lot of customers do not want to actually give all their intellectual property like a hundred percent to a partner anymore, right? They want to keep it in check.</p>
  3101. </blockquote>
  3102.  
  3103.  
  3104.  
  3105. <h2 class="wp-block-heading" id="start-here-your-path-to-becoming-the-modernization-hero">Start here: your path to becoming the modernization hero</h2>
  3106.  
  3107.  
  3108.  
  3109. <p>Whether you&rsquo;re dealing with COBOL, ancient Java, or any legacy system, here&rsquo;s how you can start today:</p>
  3110.  
  3111.  
  3112.  
  3113. <h3 class="wp-block-heading" id="start-small">Start small</h3>
  3114.  
  3115.  
  3116.  
  3117. <ul class="wp-block-list">
  3118. <li>Identify one problematic legacy system (start with fewer than 5,000 lines)</li>
  3119.  
  3120.  
  3121.  
  3122. <li>Use GitHub Copilot to analyze a single file</li>
  3123.  
  3124.  
  3125.  
  3126. <li>Document what you discover in markdown</li>
  3127.  
  3128.  
  3129.  
  3130. <li>Share findings with your team</li>
  3131. </ul>
  3132.  
  3133.  
  3134.  
  3135. <h3 class="wp-block-heading" id="build-your-ai-toolkit">Build your AI toolkit</h3>
  3136.  
  3137.  
  3138.  
  3139. <ul class="wp-block-list">
  3140. <li>Experiment with the Azure Samples framework</li>
  3141.  
  3142.  
  3143.  
  3144. <li>Learn prompt engineering for code analysis (try: &ldquo;Analyze this COBOL program and explain its business purpose in simple terms&rdquo;)</li>
  3145.  
  3146.  
  3147.  
  3148. <li>Practice iterative modernization techniques</li>
  3149. </ul>
  3150.  
  3151.  
  3152.  
  3153. <h3 class="wp-block-heading" id="think-beyond-code">Think beyond code</h3>
  3154.  
  3155.  
  3156.  
  3157. <ul class="wp-block-list">
  3158. <li>Consider nonfunctional requirements for cloud-native design</li>
  3159.  
  3160.  
  3161.  
  3162. <li>Plan for distributed systems architecture</li>
  3163.  
  3164.  
  3165.  
  3166. <li>Remember: most COBOL programs are doing simple CRUD operations. They don&rsquo;t need the complexity of a mainframe. They need the simplicity of modern architecture.</li>
  3167. </ul>
  3168.  
  3169.  
  3170.  
  3171. <p><strong>Here&rsquo;s a challenge:</strong> Find a legacy system in your organization. Six-month-old code counts as legacy in our industry. Try using GitHub Copilot to:</p>
  3172.  
  3173.  
  3174.  
  3175. <ol class="wp-block-list">
  3176. <li>Generate business logic documentation</li>
  3177.  
  3178.  
  3179.  
  3180. <li>Identify potential modernization opportunities</li>
  3181.  
  3182.  
  3183.  
  3184. <li>Create a migration plan with human validation checkpoints</li>
  3185. </ol>
  3186.  
  3187.  
  3188.  
  3189. <p>Share your results on LinkedIn and tag me. I&rsquo;d love to see what you discover.</p>
  3190.  
  3191.  
  3192.  
  3193. <h2 class="wp-block-heading" id="the-best-time-to-start-is-now">The best time to start is now</h2>
  3194.  
  3195.  
  3196.  
  3197. <p>The most powerful insight from my conversation with Julia is this: <strong>AI doesn&rsquo;t replace developer expertise. It amplifies it.</strong></p>
  3198.  
  3199.  
  3200.  
  3201. <p>COBOL experts bring irreplaceable domain knowledge. Modern developers bring fresh perspectives on architecture and best practices. AI brings pattern recognition and translation capabilities at scale.</p>
  3202.  
  3203.  
  3204.  
  3205. <p>When these three forces work together, legacy modernization transforms from an impossible challenge into an achievable project.</p>
  3206.  
  3207.  
  3208.  
  3209. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  3210. <p>The best time to modernize legacy code was 10 years ago. The second-best time is now.</p>
  3211. </blockquote>
  3212.  
  3213.  
  3214.  
  3215. <p>Special thanks to Julia Kordick, Microsoft Global Black Belt, who shared her insights and experiences that made this blog post possible.</p>
  3216.  
  3217.  
  3218.  
  3219. <p><strong>Ready to dive deeper?</strong> Check out the full blog post about this project at<a href="https://devblogs.microsoft.com/all-things-azure/how-we-use-ai-agents-for-cobol-migration-and-mainframe-modernization/"> aka.ms/cobol-blog</a> and connect with <a href="https://www.linkedin.com/in/julia-kordick/">Julia on LinkedIn</a> for the latest updates.</p>
  3220.  
  3221.  
  3222.  
  3223. <p>The age of legacy code doesn&rsquo;t have to be a barrier anymore. With the right AI tools and framework, even 65-year-old COBOL can become approachable, maintainable, and modern.</p>
  3224.  
  3225.  
  3226.  
  3227. <div class="wp-block-group post-content-cta has-global-padding is-layout-constrained wp-block-group-is-layout-constrained">
  3228. <p><strong>What legacy system will you modernize next?</strong> Start building now with <a href="https://github.com/copilot">GitHub Copilot</a> now &gt;</p>
  3229. </div>
  3230. </body></html>
  3231. <p>The post <a href="https://github.blog/ai-and-ml/github-copilot/how-github-copilot-and-ai-agents-are-saving-legacy-systems/">How GitHub Copilot and AI agents are saving legacy systems</a> appeared first on <a href="https://github.blog">The GitHub Blog</a>.</p>
  3232. ]]></content:encoded>
  3236. <post-id xmlns="com-wordpress:feed-additions:1">91444</post-id> </item>
  3237. </channel>
  3238. </rss>
  3239.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//github.blog/feed/

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda