Repository navigation
task-release: Fix the formatting of the Markdown it writes - #119
Merged
jtrobles-cdd merged 2 commits intoSep 14, 2026
Merged
Conversation
- GitHub renders the summary of each step as a Markdown document of its own and joins them with a blank line, so the reviewers, written by a later step than the rest, ended up as a list of their own rather than as the last item of the one above them. - The summary is therefore written last, by a step that does nothing else, out of the outputs of the steps that produced the values. The step that requests the reviews now records the users in outputs instead of writing them to the summary itself. - The step runs unless the run was cancelled, rather than only on success, so that a failure after the pull request was opened still leaves its URL in the summary. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jtrobles-cdd
force-pushed
the
claude/release-deploy-notification-format-128b67
branch
from
September 14, 2026 14:20
62ec126 to
be4616e
Compare
jtrobles-cdd
changed the title
- GitHub renders every newline of a comment as a line break, so a hard-wrapped checklist item reaches the pull request broken across lines. The items this workflow contributes were already joined by a line continuation, but nothing said so to the callers that supply their own, and theirs arrive wrapped. The description of both inputs now states it. - The continuation of the common pre-deployment item was aligned under the text it continues, and that alignment survived the join as a run of seven spaces in the comment body. It now continues without indentation, as the tip above it already does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jtrobles-cdd
force-pushed
the
claude/release-deploy-notification-format-128b67
branch
from
September 14, 2026 14:26
be4616e to
e4651a0
Compare
|
jtrobles-cdd
deleted the
claude/release-deploy-notification-format-128b67
branch
September 14, 2026 14:33
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The task writes Markdown in two places, the job summary and the checklist comment, and both came out malformed because of how GitHub renders it: every newline of a comment becomes a line break, and the summary of each step is a Markdown document of its own that GitHub joins to the next with a blank line. The reviewers, written by a later step than the rest of the summary, came out as a list of their own rather than as the last item of the list above them.
Job summary
- **Reviewers:** nobodynow depends onrequest_reviews_from_change_authorsbeing on, rather than on the review step having run at all.Checklist comment
*_deployment_checklist_itemsinputs now state that an item must not be hard-wrapped. Nothing said so before, which is how wrapped items reached a comment.Not fixed here