base on A command-line tool to generate GitHub and GitLab activity graph. # Generate Git Commits A command-line tool that generates GitHub or GitLab activity graphs to make it look like you have been coding regularly. <img src="https://dl.dropboxusercontent.com/s/q2iinti6v0zbhzs/contributions.gif?dl=0" alt="How it works" /> ## How To Use 1. Ensure you have [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) and [Node.js](https://nodejs.org/en/download/) installed on your machine. 2. Generate your commits: ```shell script npx fake-git-history ``` This command creates a my-history folder and generates commits with the following default settings: - Date range: Last 365 days - Commits per day: Between 0 and 4 - Frequency: Commits generated for approximately 80% of days - Distribution: Evenly distributed throughout the day 3. Create [a private repository](https://github.com/new) called `my-history` in your GitHub or GitLab, and push the changes: ```shell script cd my-history git remote add origin [email protected]:<USERNAME>/my-history.git git push -u origin master ``` Done! Now take a look at your GitHub profile 😉 ## Support This Project If you rely on this tool and find it useful, please consider supporting it. Maintaining an open source project takes time, and a cup of coffee would be greatly appreciated! <a href="https://www.buymeacoffee.com/artiebits" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a> ## Customizations ### `--preview` If you want to preview the activity graph before creating any commits, use the `--preview` flag: ```shell script npx fake-git-history --preview ``` You can combine it with other options: ```shell script npx fake-git-history --preview --distribution workHours --frequency 100 ``` ### `--frequency` Control the chance (0-100%) of generating commits for each day. This makes your activity graph look more random and realistic. The default value is `80`, which means commits will be generated for 80% of the days in the date range. Setting a lower value will randomly skip more days: ```shell script npx fake-git-history --frequency 50 ``` This will generate commits for approximately 50% of the days in your date range, making the pattern look more natural. ### `--distribution` Choose the distribution pattern for generating commits: - `uniform` (default): Evenly distributed random commits between min and max - `workHours`: More commits during work hours (9am-5pm) and on weekdays (especially Tuesday-Thursday) - `afterWork`: More commits during evenings and weekends #### Work Hours Pattern For a typical work schedule pattern that shows more activity during weekdays: ```shell script npx fake-git-history --distribution workHours --preview ``` Days between Tuesday and Thursday will have the most activity, while weekends will be mostly empty. #### After Work Pattern For an evening/weekend coder pattern that shows more activity during off-hours: ```shell script npx fake-git-history --distribution afterWork --preview ``` Saturday and Sunday will have the most activity, with Friday evenings also showing higher commit counts. ### `--startDate` and `--endDate` By default, the script generates GitHub commits for every day within the last year. But if you want to generate activity for specific dates, use these options: ```shell script npx fake-git-history --startDate "2020/09/01" --endDate "2020/09/30" ``` ### `--commitsPerDay` Specify the number of commits to create for each day. The default is `0,4`,but you can change it: ```shell script npx fake-git-history --commitsPerDay "0,6" ``` ## PS This tool was created as a joke, so please don't take it seriously. While cheating is never encouraged, if someone is judging your professional skills based on your GitHub activity graph, they deserve to see a rich activity graph 🤓 ", Assign "at most 3 tags" to the expected json: {"id":"7930","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"