Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt

Use this file to discover all available pages before exploring further.

A synthetic git data generator creates source-control sample data for branches, commit dates, commit log entries, commit messages and commit SHAs. It gives developer-tool teams repeatable Git-shaped data without copying real repository history into demos, parser fixtures or lower-control test environments.
Generate sample git data at spotzee.com/tools/git-generator.

​
Why this matters

Repository dashboards, changelog previews, CI parsers and import tools all need values that behave like Git history. Real repository logs don’t belong in support screenshots, fixture files or public demos. Git fields also expose small parser and UI issues. Commit entries include line endings and author blocks. SHA values may need shorter display variants. Branch names wrap. But hand-written sample logs get stale fast. Generated values are test fixtures only. They do not prove real commits, branches, authors or repository activity. Each Extended API call deducts a small per-call amount from your Spotzee credit balance. See the Spotzee pricing page for live per-tool pricing.

​
How it works

1

Send the request

POST to /generic/data/generate/git with count. The count is a string from 1 to 100.
2

Choose a method

Use method=profile for expanded git records, or choose one field method: branch, commitDate, commitEntry, commitMessage or commitSha.
3

Set git options

Send locale where supported, an optional numeric seed for repeatable fixtures, refDate for date-aware output, eol for commit-entry line endings, merge for merge-line output and commitShaLength for SHA length.
4

Read the response

The response returns data.git[], generated, locale, optional seed, and the resolved method. Profile records can include branch, commit date, ISO commit date, commit entry, commit message and commit SHA fields.

​
Method reference

MethodOutputMain parameters
profileExpanded source-control recordcount, locale, seed, eol, merge, commitShaLength
branchBranch-name fixturecount, locale, seed
commitDateCommit date fixturecount, locale, seed, refDate
commitEntryCommit log-entry fixturecount, locale, seed, refDate, eol, merge
commitMessageCommit-message fixturecount, locale, seed
commitShaCommit SHA fixturecount, locale, seed, commitShaLength
Use profile when you need fuller git test data. Use a field method when your form, table, parser or import job only needs one value type.

​
What to watch for

  • Count outside 1 to 100. One request generates up to 100 git records. For more rows, call the endpoint again and vary the seed when you need a different batch.
  • Wrong method for the fixture. Use profile for branch, date, entry, message and SHA fields together, or a field method for one value type.
  • Invalid reference date. refDate must be an ISO 8601 date-time with a time-zone offset, such as 2024-01-15T12:00:00.000Z, or left blank.
  • Invalid SHA length. commitShaLength must be a positive whole number from 1 to 40.
  • Unexpected line endings. Use eol=LF for Unix-style fixture text or eol=CRLF when Windows-style commit-entry output is needed.
  • Assuming real history. Generated git values are synthetic sample data. Do not treat them as evidence of real repository activity.

​
FAQs

A synthetic git data generator can return git[] records with method and value fields. Profile output can also include branch, commitDate, commitDateIso, commitEntry, commitMessage, commitSha and commitShaLength fields. The exact fields depend on the selected method.
Yes. Choose commitEntry when you need a full log-entry fixture, or commitMessage when you only need message-shaped text. Use a numeric seed when the same random commit generator output must repeat in tests.
Yes. Set a numeric seed to reproduce output for the same count, locale, method and option values. Leave the seed blank when you want a fresh random batch for exploratory testing.
Choose commitSha when you need SHA-only fixture values, then set commitShaLength from 1 to 40. Choose profile when you want commit SHAs alongside branches, dates, entries and messages.
Yes. Use method=branch when you need branch-name fixtures for forms, filters, tables or repository previews. The output is synthetic sample data for tests and prototypes.
Read the git data generator guide for endpoint options, response fields and integration patterns. The guide also shows where git fixture data fits beside date, company, contact and commerce generators.

​
Try it

Generate sample git data in the browser at spotzee.com/tools/git-generator, or call the Extended API when you need git fixtures inside automated tests and seed scripts.