From 13a469362a209c13bec3fdc1e20445dc201caa08 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Tue, 11 Nov 2025 17:18:50 +0000 Subject: [PATCH] Exclude development/infrastructure changes from release notes Users don't care about CI/CD improvements, release workflows, build processes, or testing infrastructure. Only include user-visible changes. Related to #671 --- scripts/generate-release-notes.sh | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/scripts/generate-release-notes.sh b/scripts/generate-release-notes.sh index 28c7b33..a8dec98 100755 --- a/scripts/generate-release-notes.sh +++ b/scripts/generate-release-notes.sh @@ -129,11 +129,14 @@ Guidelines: - Use bold for feature/component names followed by colon - Do NOT include commit hashes - they clutter the release notes - Only include issue references like (#123) if explicitly mentioned in commit messages -- Focus on user-visible changes only +- Focus ONLY on user-visible changes - exclude all development/infrastructure changes +- EXCLUDE: CI/CD changes, release workflow improvements, build process changes, development tooling, testing infrastructure +- EXCLUDE: Anything about "release notes generation", "automated release", "validation scripts", "GitHub workflows" +- INCLUDE ONLY: Features users interact with, bug fixes users experience, performance improvements users notice - Use clear, non-technical language - Group related changes together logically - If there are no breaking changes, write "None" in that section -- Keep the Notes section practical and actionable +- Keep the Notes section practical and actionable for end users EOF # Call LLM API based on provider