Skip to main content
Back to Dev generators

Dev

Dummy Git Commit Message Generator

Used by developers, writers, and creators worldwide.

A dummy git commit message generator saves time when you need a convincing commit history for demos, tutorials, or test repositories. Instead of hand-crafting dozens of fake log entries, generate realistic messages in seconds — formatted as conventional commits, casual one-liners, or verbose multi-line descriptions. Developers reach for fake commit histories when building portfolio projects that need a lived-in look, recording screencasts where a sparse log would distract viewers, or stress-testing tools that parse git logs. Control three variables: commit count, style, and whether to include a short hash prefix. Conventional format suits commitlint demos; casual style fits general tutorials; verbose mode adds body text for showing full git log output.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Set the count field to the number of commit messages you need, between 1 and 50.
  2. Choose a commit style: conventional for typed prefixes, casual for plain messages, or verbose for commits with a body.
  3. Toggle the include hash option to show or hide the short SHA prefix on each line.
  4. Click Generate to produce the commit history, then review the output for a mix you are happy with.
  5. Copy the full block or individual lines and paste them into your demo repo script, slide, or documentation.

Use Cases

  • •Populating a portfolio GitHub repo with a realistic-looking conventional commit history
  • •Recording a git workflow screencast without exposing real project commits
  • •Testing a semantic-release or conventional-changelog pipeline with typed commit prefixes
  • •Building a demo git repository using git commit --allow-empty in a shell script loop
  • •Creating slide-deck screenshots that show a believable feature branch and fix log

Tips

  • →Generate two separate batches — one conventional, one casual — then manually interleave them to avoid a suspiciously uniform log.
  • →If screenshotting, generate exactly 8 to 12 commits so the full list fits in one terminal window without scrolling.
  • →Turn hashes off when using messages as raw git commit -m input; turn them on for terminal screenshot realism.
  • →Edit only the scope token in conventional commits (the word in parentheses) to instantly tailor messages to your project's domain.
  • →Use the verbose style when demonstrating git log --stat or GitHub's commit detail view, where a body paragraph looks expected.
  • →For changelog tool demos, generate 20 or more commits so the resulting changelog has multiple sections — fixes, features, and chores.

FAQ

how do i make generated commits look like they belong to my project

Generate a batch, then edit the scope tokens — swap (api) for (checkout) or (auth) to match your domain. The action verbs and structure are already realistic, so small scope edits usually make the log feel project-specific without rewriting every line.

are the commit hashes real git sha values

No. They are randomly generated 7-character hex strings that mimic the short SHA git displays in git log --oneline output. They have no cryptographic link to any real commit object, so don't use them in scripts that query an actual repository.

what is the difference between conventional casual and verbose commit styles

Conventional uses typed prefixes like feat, fix, and chore — ideal for commitlint or changelog tooling demos. Casual produces natural-language messages without prefixes, closer to how many developers actually commit. Verbose adds a body paragraph below the subject line, useful when demonstrating git log formats that display full commit bodies.