A changelog generator needs a commit history to parse, and writing forty conventional commits by hand is tedious. These come with correct type, scope and breaking-change markers, plus the hashes and stats a log view needs.
What you can control
- Conventional Commits with proper type, optional scope, and the
!breaking-change marker. - Full 40-character hashes plus the 7-character short form, both from the same value.
- Branch names derive from the commit subject, matching the convention most teams follow.
- Diff statistics — files, insertions, deletions — for testing a commit list or a contribution graph.
Testing ideas
- Changelogs. Generate Conventional Commits with breaking changes to test semantic-release and changelog tooling.
- Gitmoji. Emoji in commit messages test terminal and web renderers.
- Bodies. Include commit bodies to test multi-line message handling.
- Hashes. Full and short hashes test link generation to your code host.
What this is not
Hashes are random hex rather than real SHA-1 digests of any tree. They have the right shape and will not match anything in a real repository.