merge-changelog

You can merge changelog fragments by grouping them by date, inserting new entries into existing CHANGELOG.md sections, and deleting processed fragment files. The workflow also creates a git commit to maintain a clean repository state.

Consolidating changelog fragments before a git merge involves aggregating date-based fragments into CHANGELOG.md while avoiding duplicate entries. Processed fragment files are removed and a commit is created to finalize the documentation cleanup.

Duplicate-aware insertion checks existing CHANGELOG.md date sections and appends only new fragment entries. This prevents redundant changelog records while keeping related changes grouped under their respective dates.

Manual deletion of changelog fragment files is unnecessary after merging. The process automatically removes processed fragment files and creates a git commit to ensure the documentation directory remains clean for future updates.

This approach supports routine documentation cleanup on the main branch. It applies to release preparation and main-branch integration workflows by consolidating scattered changelog fragments into a single CHANGELOG.md file.