Update add_reaction job to always create new comments and add comment-repo output

[Copilot]

✅ Complete: Update add_reaction Job to Always Create New Comments

Changes Required

• Analyze current implementation
• Update JavaScript logic to always create new comments (never edit)
• Ensure comment-id output is set for all scenarios (including repo info)
• Add comment-repo output for downstream job use
• Update tests to verify new behavior
• Run all tests to ensure no regressions
• Verify the changes work correctly
• Add periods at end of workflow link text sentences
• Add GraphQL comment creation support for discussion_comment events

Summary of Changes

JavaScript Changes (add_reaction_and_edit_comment.cjs):

• Removed the conditional logic that checked whether to create or edit comments
• Now always creates new comments for all event types (issues, pull_request, issue_comment, pull_request_review_comment, discussion, discussion_comment)
• Added comment-repo output containing the repository in owner/repo format
• Simplified the logic by removing GET and PATCH operations for editing
• Added periods at end of workflow link text for proper punctuation
• Implemented full GraphQL support for discussion_comment events to create new comments on discussion threads using the addDiscussionComment mutation

Go Changes (compiler.go):

• Added comment_repo to the activation job outputs map
• Ensures downstream jobs can access the repository information

Test Updates:

• Added 3 new JavaScript tests verifying new comments are always created
• Updated existing tests to verify comment-repo output
• Updated discussion_comment test to verify GraphQL comment creation behavior
• Updated Go tests to check for comment_repo in the generated YAML
• All 534 JavaScript tests pass ✅
• All Go tests pass ✅

Verification

✅ No GET or PATCH operations remain in generated lock files
✅ comment-repo output present in all lock files
✅ All workflows recompiled with updated JavaScript
✅ Behavior verified: comments are always created (never edited)
✅ Proper punctuation added to all workflow link text
✅ Full GraphQL support for both discussion and discussion_comment events

Original prompt

Update the JavaScript that implements the add_reaction job to NOT edit existing comments and instead always create a new comment. The comment id and comment repo should be an output of the add_reaction job so that it can be reused by other jobs.Agentic Plan for add_reaction Job Update

Objective:
Modify the add_reaction job in JavaScript to ensure it no longer edits existing comments, and instead always creates a new comment. Additionally, the job should output the new comment ID and associated repository for downstream use by other jobs.

Plan Steps:

Review Current Implementation
Inspect the current add_reaction job logic to identify where it searches for and edits existing comments.
Locate the code handling the output of comment identifiers.
Update Comment Creation Logic
Remove or disable the conditional logic that checks for existing comments.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pelikhan]

@copilot add a dot at the end of the sentence.

[Copilot]

Added periods at the end of the workflow link text sentences in commit 0c7e9a3.

[pelikhan]

@copilot add support for discussion and discussion-comment event (use graphql)

[Copilot]

@copilot add support for discussion and discussion-comment event (use graphql)

Added GraphQL comment creation support for discussion_comment events in commit 9ea5fa9. Discussion events already had full GraphQL support. Both now create new comments on discussion threads using the addDiscussionComment mutation.

[github-actions]

Agentic Changeset Generator triggered by this pull request.