/changelog · Entire

Changelog Generation

Generate a changelog entry for a new release by analyzing merged PRs since the last tag.

Parameters

The user provides:

Step 1: Gather Data

  1. Find the previous release tag: git tag --sort=-version:refname | head -1
  2. List all merge commits since that tag: git log <tag>..HEAD --merges --format='%s' | grep -v "Merge branch"
  3. Get PR details with: gh pr list --state merged --base main --search "merged:><tag-date>" --json number,title,author --limit 50
  4. List contributors: git log <tag>..HEAD --format='%an' --no-merges | sort | uniq -c | sort -rn

Step 2: Identify External Contributors

To determine if a contributor is external, check for an @entire.io email:

1

git log --all --format='%an <%ae>' --author="<name>" | sort -u

If they have an @entire.io email anywhere in git history, they are internal. Only list external contributors in the Thanks section.

Also check the memory file at memory/project_team_members.md for known internal/external mappings.

Step 3: Write the Entry

Insert the new version section at the top of CHANGELOG.md, after the header and before the previous version.

Format

Follow the existing style in CHANGELOG.md exactly:

## [X.Y.Z] - YYYY-MM-DD

### Added

- Feature description with context ([#123](https://github.com/entireio/git-sync/pull/123))

### Changed

- Change description ([#456](https://github.com/entireio/git-sync/pull/456))

### Fixed

- Bug fix description ([#789](https://github.com/entireio/git-sync/pull/789))

### Housekeeping

- Maintenance item ([#101](https://github.com/entireio/git-sync/pull/101))

### Thanks

Thanks to @contributor for description of contribution!

Style Rules

Categorization Guide

Changelog Entry

Added the 0.6.0 entry (dated 2026-06-03) to the top of CHANGELOG.md:

Notes: