<?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: Repo Rescue</title>
    <description>The latest articles on DEV Community by Repo Rescue (@repo_rescue).</description>
    <link>https://dev.to/repo_rescue</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%2F4160569%2Fb9c09155-871d-44e8-bb13-dfff3e52018a.jpg</url>
      <title>DEV Community: Repo Rescue</title>
      <link>https://dev.to/repo_rescue</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/repo_rescue"/>
    <language>en</language>
    <item>
      <title>Your GitHub PRs Tell What You Built. Repo Rescue Tells How You Built It.</title>
      <dc:creator>Repo Rescue</dc:creator>
      <pubDate>Sun, 04 Oct 2026 06:47:42 +0000</pubDate>
      <link>https://dev.to/repo_rescue/your-github-prs-tell-what-you-built-repo-rescue-tells-how-you-built-it-1nkg</link>
      <guid>https://dev.to/repo_rescue/your-github-prs-tell-what-you-built-repo-rescue-tells-how-you-built-it-1nkg</guid>
      <description>&lt;p&gt;GitHub is great at showing what you contributed to open source.&lt;br&gt;
You can see the issues you worked on, the pull requests you opened, the commits you made, and whether your PR was merged.&lt;br&gt;
But there is a lot more to an engineering contribution than the final PR.&lt;br&gt;
Why did you work on that issue?&lt;br&gt;
How did you investigate it?&lt;br&gt;
What approach did you take?&lt;br&gt;
What trade-offs did you make?&lt;br&gt;
What did you learn?&lt;br&gt;
That's the idea behind Repo Rescue.&lt;br&gt;
What is Repo Rescue?&lt;br&gt;
Repo Rescue is an engineering journal for your open-source contributions.&lt;br&gt;
Instead of treating a contribution as simply:&lt;br&gt;
Issue → PR → Merged&lt;/p&gt;

&lt;p&gt;we want to capture the engineering journey behind it:&lt;br&gt;
Problem → Investigation → Approach → Techniques → Implementation → Trade-offs → Result → Lessons Learned&lt;/p&gt;

&lt;p&gt;The goal is to build a record of the engineering work you actually do in open source.&lt;br&gt;
Getting started takes almost no effort&lt;br&gt;
You don't need to manually add your GitHub repositories or enter every PR.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Repo Rescue
Go to:
&lt;a href="https://repo-rescue.vercel.app/contributions" rel="noopener noreferrer"&gt;https://repo-rescue.vercel.app/contributions&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sign in with GitHub
That's it.
Once you're signed in, wait for Repo Rescue to sync your contributions.
The system will discover your GitHub contribution history and link it to your Repo Rescue account.
You don't have to manually build your profile.
Track your contributions
Once your contributions are synced, you can see the work you've actually done across GitHub.
You can explore your PRs and their lifecycle, including whether they're:&lt;/li&gt;
&lt;li&gt;Merged&lt;/li&gt;
&lt;li&gt;Open&lt;/li&gt;
&lt;li&gt;Closed
The idea is to give you a single place to understand your open-source contribution history rather than having to dig through GitHub repositories one by one.
But we're trying something else too
Open source can be incredibly competitive.
People contribute to hundreds of repositories, solve difficult issues, review code, and build things that millions of developers use.
But there isn't really a place where you can turn that activity into a competitive engineering environment.
So Repo Rescue has a global leaderboard.
You can see how your verified open-source contributions compare with contributors around the world.
The important part is that we're not asking you to enter your achievements manually.
Your contribution history comes from GitHub.
We're experimenting with whether competition can make contributing to open source more engaging and motivating.
This is still an MVP
And honestly, we don't know if we've got the idea right yet.
Maybe developers don't want an engineering journal.
Maybe GitHub already provides everything they need.
Maybe documenting the reasoning behind a contribution is too much work.
Maybe a global leaderboard makes open source more fun.
Maybe it makes it worse.
That's what we're trying to find out.
So if you contribute to open source, I'd love for you to try it and poke holes in it.
Don't just tell me what you like.
Tell me what's unnecessary.
Tell me what's confusing.
Tell me what you'd change.
Tell me why you wouldn't use it.
Try it
You literally just need to:&lt;/li&gt;
&lt;li&gt;Open &lt;a href="https://repo-rescue.vercel.app/contributions" rel="noopener noreferrer"&gt;https://repo-rescue.vercel.app/contributions&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sign in with GitHub&lt;/li&gt;
&lt;li&gt;Wait for your contributions to sync&lt;/li&gt;
&lt;li&gt;Explore your PRs and contribution history&lt;/li&gt;
&lt;li&gt;Check out the global leaderboard
Then tell me what you think.
Repo Rescue: &lt;a href="https://repo-rescue.vercel.app/contributions" rel="noopener noreferrer"&gt;https://repo-rescue.vercel.app/contributions&lt;/a&gt;
I'd especially love feedback from developers who actively contribute to open source.
Poke holes in the idea.
You can leave a comment below or reach us at &lt;a href="mailto:repo.rescue.rr@gmail.com"&gt;repo.rescue.rr@gmail.com&lt;/a&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%2F3n986a6l2jrobbk3bcsx.png" alt=" " width="800" height="425"&gt;
Try Repo Rescue: &lt;a href="https://repo-rescue.vercel.app/contributions" rel="noopener noreferrer"&gt;https://repo-rescue.vercel.app/contributions&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>opensource</category>
      <category>startup</category>
      <category>webdev</category>
      <category>github</category>
    </item>
  </channel>
</rss>
