From 0c962661ca33bb5a284f5c11d62b61868db09619 Mon Sep 17 00:00:00 2001 From: Gabriele De Rosa Date: Mon, 27 Apr 2026 15:53:42 +0200 Subject: [PATCH] fix(prompt): reduce duplication by merging overlapping PR and commit details Replace vague grouping instruction with explicit rules to identify distinct changes, combine overlapping PR/commit details, and merge related items into a single bullet. Bump version to 2.0.2. --- README.md | 4 ++-- action.yml | 8 +++++++- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7f447be..540020c 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ GitHub Action to generate a `CHANGELOG.md` on new tags, with optional Telegram n ## Breaking changes in 2.x -- The action now lives at the repository root and is used as `Waveful/ChangelogAction@v2.0.1`. +- The action now lives at the repository root and is used as `Waveful/ChangelogAction@v2.0.2`. - The old split actions (`/generate`, `/notify`, `/annotate`) have been removed from the default setup. - Changelog generation is always the default behavior. - Telegram notification only runs when `telegram-bot-token`, `telegram-chat-id`, and `changelog-url` are all provided. @@ -67,7 +67,7 @@ jobs: steps: - name: Run changelog action id: changelog - uses: Waveful/ChangelogAction@v2.0.1 + uses: Waveful/ChangelogAction@v2.0.2 with: github-token: ${{ secrets.GITHUB_TOKEN }} target-branch: master diff --git a/action.yml b/action.yml index ebdf5c6..e35b8bc 100644 --- a/action.yml +++ b/action.yml @@ -260,7 +260,13 @@ runs: Start with a level-2 heading using the current tag. Use the bullet symbol "•" for every list item. Keep the language simple, concise, and understandable for non-technical readers. - Group related changes together when it improves readability. + + Before writing, read all provided information and identify the distinct changes. + PR details and commit details may overlap; combine them, do not duplicate. + Merge multiple items addressing the same feature, bug, or area into a single bullet. + Never describe the same change more than once. + Focus on what changed from the user's perspective rather than listing every commit or PR. + Ignore automation-only changes unless they materially affect users. Do not add any introduction, analysis notes, or closing text. EOF