Git Log Parser

How to use this developer tool

1. Paste the supported Git, changelog, or description text.
2. Adjust the available options when the page provides them.
3. Select Parse Log or press Ctrl/Cmd + Enter.
4. Review the summary and output, then copy or download it.

What this developer tool does

The output reflects the fields and conventions that can be derived from the supplied text. Counts and warnings are calculated from the parsed result rather than estimated from repository history.

All processing stays in the browser tab. No repository credentials or network request are required.

Example

Input

commit a1b2c3d
Author: Ada Lovelace <ada@example.com>
Date:   Fri Jul 18 10:15:00 2026 +0900

    feat(parser): add quoted field support

commit d4e5f6a
Author: Lin Kim <lin@example.com>
Date:   Thu Jul 17 09:00:00 2026 +0900

    fix: handle empty input

Output

Run the sample to see the exact generated output and calculated metrics.

Use cases

• Prepare repository metadata before review.
• Standardize repeated Git and release tasks.
• Inspect pasted output without sharing repository access.
• Export structured data for documentation or automation.

Tips for reliable output

• Copy raw output rather than screenshots.
• Keep identifiers and version numbers unchanged.
• Review generated prose before publishing.
• Test unusual multiline and empty-field cases.
• Treat Git itself as the source of truth.

Processing details

The parser works on plain text and uses deterministic JavaScript rules tailored to Git Log Parser. It does not execute Git commands or inspect a local repository.

Formatting can vary between Git aliases, hosting platforms, and team conventions. If a custom format is not recognized, convert it to the sample structure or verify the result manually.