<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: DebtDraft</title>
    <description>The latest articles on DEV Community by DebtDraft (@debtdraft).</description>
    <link>https://dev.to/debtdraft</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4177977%2F5a35162b-794a-4c1d-bb03-03d6c9736473.png</url>
      <title>DEV Community: DebtDraft</title>
      <link>https://dev.to/debtdraft</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/debtdraft"/>
    <language>en</language>
    <item>
      <title>Know your pull request's health before you merge it</title>
      <dc:creator>DebtDraft</dc:creator>
      <pubDate>Mon, 12 Oct 2026 01:08:02 +0000</pubDate>
      <link>https://dev.to/debtdraft/know-your-pull-requests-health-before-you-merge-it-78</link>
      <guid>https://dev.to/debtdraft/know-your-pull-requests-health-before-you-merge-it-78</guid>
      <description>&lt;p&gt;Most code health problems do not arrive in one big commit. They arrive one reasonable pull request at a time: a function that grows a little too complex, a dependency that falls behind, a change that ships without tests. By the time anyone notices, the problem is everywhere.&lt;/p&gt;

&lt;p&gt;DebtDraft is a GitHub Action that makes that visible at the moment it matters, &lt;strong&gt;inside&lt;/strong&gt; the pull request.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;On every pull request and every push to your default branch, DebtDraft scores your repository on five signals:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Code complexity&lt;/li&gt;
&lt;li&gt;Test coverage&lt;/li&gt;
&lt;li&gt;Duplication&lt;/li&gt;
&lt;li&gt;Outdated dependencies&lt;/li&gt;
&lt;li&gt;Vulnerable dependencies&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The result is one score and one letter grade, posted as a single comment on the pull request. A separate section looks only at the lines the change touches, so you can see what this change did, not just the state of the whole repository.&lt;/p&gt;

&lt;h2&gt;
  
  
  Track it over time
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjp94p04axobb3o1pqdl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjp94p04axobb3o1pqdl.png" alt="A screenshot of the dashboard tracking your repository health over time." width="800" height="433"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A hosted dashboard shows every connected repository with its current grade and its trend. You can open a repository to see the score history, and open any scan to see which functions, files and dependencies are behind the number.&lt;/p&gt;

&lt;h2&gt;
  
  
  Setup
&lt;/h2&gt;

&lt;p&gt;Add one step to your workflow, generate and add the API key, and commit the workflow. That's it!&lt;/p&gt;

&lt;h2&gt;
  
  
  Privacy
&lt;/h2&gt;

&lt;p&gt;Secrets detection runs entirely on your runner, and secrets never leave it, not even to our own dashboard. Your source code is never uploaded. Privacy is not a privilege. It's a right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;DebtDraft is free for up to three repositories right now.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Website: &lt;a href="https://debtdraft.dev?utm_source=devto" rel="noopener noreferrer"&gt;https://debtdraft.dev?utm_source=devto&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;GitHub Marketplace: &lt;a href="https://github.com/marketplace/actions/debtdraft" rel="noopener noreferrer"&gt;https://github.com/marketplace/actions/debtdraft&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We would love to hear which signal matters most to your team!&lt;/p&gt;

</description>
      <category>github</category>
      <category>devops</category>
      <category>security</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
