Gitログフォーマッター＆プリッティファイア

データ開発者文章

[iotools_git_log_formatter_prettifier]

ガイド

Gitログフォーマッター＆プリッティファイア

raw output from git log and immediately it into a clean, scannable HTML table, a copy-ready Markdown table, or a structured JSON array. The tool automatically detects the most common log formats (--oneline, --mediumと、 --pretty=fuller) and normalizes the date column, so you can directly paste the result into a release note, a pull request description, or an internal dashboard.

使用方法

でWindows上で git log in your terminal with whatever flags you prefer and copy the output.
を入力フィールドに貼り付けます。あなたが入力を終えた瞬間、ツールは画像を解码し、プレビューします。 Git Log Output textarea on the left.
離脱 入力フォーマット お 自動検出, or select the exact format you used.
[表示モード]を選択してください Date Format (ISO, short, RFC 2822, or relative) if you want to normalize timestamps.
Select your Output as target: HTML table, Markdown table, or JSON array.
Use the copy button to grab the source, the download button to save a file, or view the live HTML preview above the source code.

機能

Auto-detect formats – Recognizes --oneline, --mediumと、 --pretty=fuller output without configuration.
Three output targets – Generates a styled HTML table, a GitHub-flavored Markdown table, or a JSON array in one click.
Live HTML preview – See the rendered table above the source so you know exactly what your readers will see.
Configurable date formats – Converts Git’s default date strings to ISO 8601, short date, RFC 2822, or human-readable relative time.
Hash, author, date, subject columns – Automatically detected from the log block so the output remains compact when fields are missing.
Refs and merge commits – Preserves branch and tag refs from the header, plus the Merge: line when present.
クライアントサイドのみ – Your commit messages stay in the browser; nothing is uploaded or stored.

 よくある質問

What is the difference between the Git log oneline and medium formats?

の --oneline format prints one commit per line as <short-hash> <subject>, optionally followed by ref names in parentheses. The default --medium format prints a multi-line block per commit with the full hash on the first line and labeled Author: と Date: headers, followed by an indented commit message. Medium is more verbose but preserves authorship and timestamps; oneline is dense and ideal for scanning history.
Why does Git print dates in a non-ISO format by default?

Git inherits its default date format (RFC 2822 style, e.g. Tue Oct 10 13:55:36 2024 -0700) from older Unix mail conventions, where commits were originally exchanged as email patches. ISO 8601 is more machine-friendly, which is why Git also supports --date=iso and a number of other formats. Tools that consume log output typically normalize the date so downstream systems can sort or compare commits reliably.
What does the short hash represent in a Git commit?

Every Git commit is identified by a 40-character SHA-1 (or SHA-256 in newer repos) digest of its contents. The short hash is simply the first 7 (or more) characters of that digest. Git automatically expands as many characters as needed to remain unambiguous inside a given repository, so the short hash is a compact but still uniquely identifying reference to the commit.
What is a merge commit and how does it differ from a regular commit?

A regular commit has exactly one parent and represents a linear change on top of an existing history. A merge commit has two or more parents and joins two diverging branches back together. In git log --medium, merge commits are marked with an extra Merge: header that lists the parent hashes, which distinguishes them from feature commits.
Why are HTML and Markdown tables useful for sharing commit history?

Raw git log output is monospaced text that does not render well in most documentation systems. Converting it to an HTML or Markdown table gives each commit field its own column, lets readers scan many commits at once, and makes it possible to embed history into release notes, changelogs, wikis, or pull request descriptions where Markdown and HTML are first-class citizens.