Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 3 min read

I Built a Receipt Printer for Your GitHub Year 🧾

Press a button. A tiny printer warms up. Paper slides out, and your entire GitHub year lands in your hands as a receipt. That's Git Receipts, and you can print yours in about ten seconds. Print your GitHub year β†’ No

I Built a Receipt Printer for Your GitHub Year 🧾

Press a button. A tiny printer warms up. Paper slides out, and your entire GitHub year lands in your hands as a receipt.

That's Git Receipts, and you can print yours in about ten seconds.

Git Receipts printer feeding a receipt

Print your GitHub year β†’

No sign-in needed. Enter any public GitHub username: your own, a friend's, or a developer you admire.

This is project #1 in Beyond the Green Squares, a series where I turn GitHub activity into fun things you can try and keep.

How it works

  1. Enter a GitHub username or profile link
  2. Pick a year
  3. Press FEED and watch it print
  4. Save it, share it, or print it on real paper

The finished receipt

Why a receipt?

Everyone knows what a receipt looks like: a narrow strip of paper, neat rows, dashed lines, and a bold total at the bottom.

It fits a year of GitHub activity surprisingly well. Your contributions become the total. Active days and streaks become small details you can scan at a glance.

And there's something satisfying about it. You press a button, wait for the machine, and get a little object at the end. I wanted that moment to be part of the experience.

A printer that feels like a printer

I didn't want a box with rounded corners. The machine has an off-white body, a dark top deck, a paper slot, status lights, and a FEED button that clicks into place.

The motion matters just as much. Paper has to emerge from the slot, feed through, and get cut at the end. If it floats, the magic is gone.

If you prefer reduced motion, it skips the animation and shows your finished receipt. Sound is off by default.

The numbers stay honest

The design is playful. The data is not.

  • No guessing. If GitHub doesn't provide a number, it's left off the receipt instead of being estimated.
  • Samples are labeled. The demo receipt on the landing page is clearly marked as a sample.
  • Nothing borrowed. If a lookup fails, you see an unavailable message, never someone else's activity.

One more honest note: a contribution count can't capture everything. Reading, planning, learning, and time away from the keyboard all count as real work. The receipt is a keepsake of reported activity, not a measure of you.

Take it with you

When printing finishes, your receipt opens in a full-size viewer. Scroll through it, then keep it however you like:

  • PNG to share
  • PDF to print on paper
  • SVG and plain text
  • README embed to show it on your GitHub profile

Receipt with the achievement stamp

Hit a milestone and your receipt gets an achievement stamp, pressed onto the paper like the real thing. Every receipt also carries a QR code that leads back to it.

Put it on your GitHub profile

Your receipt can live in your profile README, and it follows light and dark mode automatically. Click it and it opens your receipt on Git Receipts.

Copy the README snippet
<a href="https://git-receipts.vercel.app/?user=YOUR_USERNAME&amp;year=2026&amp;stamp=true">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://git-receipts.vercel.app/api/receipt.svg?year=2026&amp;stamp=true&amp;user=YOUR_USERNAME&amp;theme=dark">
    <img src="https://git-receipts.vercel.app/api/receipt.svg?year=2026&amp;stamp=true&amp;user=YOUR_USERNAME&amp;theme=light" alt="YOUR_USERNAME's 2026 GitHub contribution receipt">
  </picture>
</a>

Replace YOUR_USERNAME in all three places with your GitHub username, and change the year if you want a different one.

Your turn πŸ‘€

Print your GitHub year β†’

Then tell me what caught your eye: your total, your longest streak, or a month you'd completely forgotten about. Add it to your profile README, post your receipt, and tag me. I'd love to see it.

And if you have a unique idea for turning GitHub activity into something worth keeping, drop it in the comments. The best ones might become the next post in Beyond the Green Squares, and we'll build it together.

What should we build next?

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.