dblock / slack-ruby-client

91%

master: 91%

LAST BUILD ON BRANCH include-changelog-in-commit-message

branch: SELECT

CHANGE BRANCH

x

Sync Branches

• No branch selected
• 1-item-arg-groups
• 2.5.0-connection-options
• add-code-coverage
• added-ruby-3.4
• ai-generated-changelog-entries
• calm-down-the-cron
• chat-api-patch
• fix-ai-inference-yaml-indentation
• fix-apps-user-connection-group
• fix-channel-id
• fix-ci
• fix-coveralls
• fix-files-upload-v2-multiple-files
• fix-generator
• fix-hash-inspect-format-drift
• fix-markdown-text-mutual-exclusion
• gregsaab-add_files_upload_v2
• include-changelog-in-commit-message
• master
• migrate-copilot-cli-provider
• migrate-danger-pr-comment
• milestruecar-async-cache-build-485
• oauth-file-upload-samples
• rack-3.0-rewind
• remove-rtm
• rid-code-climate
• support_channel_id_s
• test-copilot-cli
• translate-channels-file-upload

Build # 31557105933

Build Type

push

github

Committed by dblock

Commit Message

Include AI-generated changelog entries in the commit message, not just the PR body

PR #590 showed this gap: the commit message was just
'Update API from slack-api-ref@784d1d4 (2026-08-12)', with no details,
while the PR body had the full list of changes generated by the AI
CHANGELOG step. Anyone looking at git log/git blame for this commit
alone (outside the PR UI) had no idea what actually changed.

Reuse steps.entries.outputs.body_list (already computed for the PR
body) in commit-message as well, so the commit message itself carries
the same bulleted summary of changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Coverage Stats

5232 of 5746 relevant lines covered (91.05%)

100.24 hits per line