danvics/Pulse
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Exclude development/infrastructure changes from release notes

Browse source 
Users don't care about CI/CD improvements, release workflows, build
processes, or testing infrastructure. Only include user-visible changes.

Related to #671
This commit is contained in:
rcourtman 2025-11-11 17:18:50 +00:00
parent 93d0eb6b8a
commit 13a469362a
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
scripts/generate-release-notes.sh
View file

@ -129,11 +129,14 @@ Guidelines:
- Use bold for feature/component names followed by colon - Use bold for feature/component names followed by colon
- Do NOT include commit hashes - they clutter the release notes - Do NOT include commit hashes - they clutter the release notes
- Only include issue references like (#123) if explicitly mentioned in commit messages - 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 - Use clear, non-technical language
- Group related changes together logically - Group related changes together logically
- If there are no breaking changes, write "None" in that section - 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 EOF
# Call LLM API based on provider # Call LLM API based on provider