Git History Generator Logo

Git History Generator

Because commit quantity is the only true measure of a developer

Get it on GitHub

What's Git History Generator all about?

Ever noticed how some developers treat their GitHub contribution graph like a competitive sport? We think that's pretty funny, so we created Git History Generator to poke a little fun at the whole situation.

This project is a playful reminder that those green squares don't always tell the whole story. After all, we can make our contribution graph look impressive without writing a single line of meaningful code!

Don't let a graph dictate your worth as a developer. But if you must, we've got you covered!

Git History Generator Illustration

How it works

Git History Generator Before and After

Git History Generator uses a shell script to generate fake Git commits and push them to your repository. It creates a "worklog.md" file and fills it with random entries, dating them back for the number of months you specify.

The script simulates a realistic commit pattern, making more commits on weekdays and fewer on weekends. It also varies the number of commits per day to make the contribution graph look more natural. Because who doesn't work harder on Mondays, right?

Getting started

  1. Clone Git History Generator:
    git clone https://github.com/nk8/githistorygenerator.git
  2. Create a new repository on GitHub for your soon-to-be-impressive project
  3. Navigate to the Git History Generator directory:
    cd githistorygenerator
  4. Clone your new repository here:
    git clone [your-repo-url] [your-repo-name]
  5. Run the magic script:
    ./script.sh -d [your-repo-name] -m [number_of_months]
    Replace [your-repo-name] with your target repo and [number_of_months] with how far back you want to pretend you've been coding.
  6. Push your newly generated "hard work" to GitHub:
    cd [your-repo-name]
    git push
  7. Marvel at your GitHub profile and bask in the glory of your green squares!

Note: The Git History Generator script files should remain separate from your target repository. You're running the script on your target repo, not copying the script into it. We wouldn't want anyone to know your secret, would we?

Remember, this is just for fun. We don't recommend using this for any serious purposes. Unless you're trying to impress your cat. Cats love green squares.

Frequently Asked Questions

What is a GitHub contribution graph?

A GitHub contribution graph is a visual representation of a user's activity on GitHub. It displays a calendar view of the past year, with each day colored based on the number of contributions made. More contributions result in darker green squares, creating a pattern often referred to as "green squares."

Is it ethical to use Git History Generator?

Git History Generator is intended as a satirical tool to highlight the limitations of using contribution graphs as a measure of developer productivity. We do not recommend using it to misrepresent your actual work. Always strive for genuine contributions and use this tool responsibly, primarily for educational or demonstrative purposes.

How do I set up Git History Generator on my machine?

To set up Git History Generator, you'll need Git installed on your machine. Clone the repository, create a new GitHub repo for your target project, and run the provided script. Detailed instructions are available in the "Getting started" section above.

Can Git History Generator be detected?

While Git History Generator creates commits that look natural, a close inspection of the repository's history and content might reveal the generated nature of the commits. It's important to remember that this tool is meant for educational and satirical purposes, not for deceiving others.

How does Git History Generator impact my existing repositories?

Git History Generator is designed to work on a new, separate repository. It doesn't modify your existing repositories unless you explicitly run the script on them. Always use caution and consider creating a backup before running any scripts that modify your Git history.

What are some alternatives to measuring developer productivity?

Consider more holistic measures of productivity such as project completion rates, code quality metrics, peer reviews, and the impact of your work on business goals. Quality often matters more than quantity in software development.

Support Git History Generator

Enjoy using Git History Generator? Consider buying me a coffee to fuel more fun projects!

Share this on X

Found Git History Generator enlightening? Share the secret of true developer productivity!

Just discovered Git History Generator - because nothing says "10x developer" like a fully tiled contribution graph! 💻✨ Check it out at GitHistoryGenerator.com #GitHistoryGenerator #DeveloperProductivity