Use issue-specific professional acknowledgement in org bot comments#3
Merged
Conversation
Agent-Logs-Url: https://github.com/th30d4y/.github/sessions/472a6b14-9833-4120-913c-4e67bf30ba16 Co-authored-by: Stalin-143 <161853795+Stalin-143@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
0x5t4l1n
April 22, 2026 21:53
View session
|
👋 Hello! Thanks for your contribution. We will review this and get back to you as soon as possible. — th30d4y |
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
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.
Issue openings were not receiving the intended professional acknowledgement text. The workflow now differentiates message content by event type so issues get a review-oriented response while PR behavior remains unchanged.
Problem addressed
Workflow change
.github/workflows/org-bot.ymlinPost welcome commentto choose message text based oncontext.eventName.BOT_MESSAGEenv usage for this step and generated the message inline in script logic.Behavior after change
issuesevent: posts an issue-specific professional acknowledgement.pull_requestevent: keeps the existing contribution acknowledgement.