Git Faker 3000

How it works

GitHub stores your commit history as metadata on your machine. Every time you push, your local commits get synced to GitHub's servers. That metadata is what paints the green squares on your profile. Git Faker 3000 works directly with that local metadata to create commits that look exactly like real ones.

The idea

When you make a real commit, Git records a timestamp, an author name, and an email. It also stores a parent commit reference that chains your history together. All of this lives in your local .git folder. GitHub reads it and draws the contribution graph on your profile. Nothing stops you from creating commits with whatever dates and counts you want, as long as they form a valid Git history.

How we do it

First, you connect your GitHub account. We need access so we can create a temporary repository under your name. Nothing touches your existing repos.

Next, you design your contribution pattern. Pick the years you want to fill in, choose an intensity style, and the tool calculates exactly how many commits to create for each day. You can go subtle with a few extra squares or go all in with a fully green grid.

Then we build the commits. Each commit gets a proper timestamp, a realistic commit message, and gets linked into a valid Git chain. The whole thing runs in isolation so nothing mixes with your real work.

Finally, we push everything to a fresh private repo on your GitHub account. The contribution graph updates automatically because GitHub counts all commits across all your repos, including private ones. You can delete the repo afterwards and the green squares stay.

Is it safe?

All generated commits go into a separate repo you control. Your real repos and real work are never touched. You can delete the generated repo at any time and nothing breaks. The contribution squares on your profile are just a count, they don't link back to any specific repo.