Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "I built a free GitHub profile README generator with no badge APIs, no backend and a 3D contribution universe" | Hashnode

Feed/

Discussion

komal Sandeep

Brainstorm Mode

Oct 16

I built a free GitHub profile README generator with no badge APIs, no backend and a 3D contribution universe

Your GitHub profile is often the first thing a recruiter, a hiring manager or a possible collaborator sees. For most of us it's a contribution graph and six pinned repos. That's a missed chance. So I

sandeepkomal.hashnode.dev6 min read

#github #github-actions #opensource #javascript #web-development #developer-tools #github-readme

Responses5

Markdown supported · ⌘↵ to post

StackShortlist

Proof Over Promises.

Skipping badge APIs is a smart call, since third party badge services going down or rate limiting is one of the most common reasons profile READMEs show broken images. If the 3D contribution view is generated by a GitHub Action, committing the output as a static SVG on a schedule keeps the profile fast and avoids hitting the API on every page view. A note on how often it refreshes would help people set expectations.

Oct 16

StackShortlist

Proof Over Promises.

Oct 17

The per-profile offset worked out from the username is a nice touch, it spreads the runs without anyone setting a cron by hand. The 60 day pause on scheduled workflows is the one I'd put in bold in that note, since a profile can quietly go stale and look broken.

komal Sandeep

Brainstorm Mode

Oct 17

Thanks! Yes, the offset means nobody has to pick a cron time, and thousands of profiles don't all hit GitHub at 00:00.

Good call on the 60-day pause. It's the one that bites quietly: a profile that isn't changing doesn't produce commits, so a quiet repo is exactly the kind that gets paused. I've moved it to the top of the note and put it in bold. Appreciate the review! 🙏

StackShortlist

Proof Over Promises.

Oct 17

Putting it at the top makes sense. The staggered offset is a nice touch too, since nobody has to think about cron syntax to get a sane schedule.