Skip to content

Improve Actions workflow that sends notification about issue comment to send Slack notification when bot comment was skipped #31

Closed

Description

@MisRob

Summary

Adjust .github/workflows/contributor-issue-comment.yml workflow to send a notification to #support-dev-notifications Slack channel when a bot response was intentionally skipped on an issue due to the optimization that ensures that no more than one bot reply is sent per an hour. The text of the notification should be: "[repo] Bot response skipped on issue: Test issue (less than 1 hour since last bot reply)"

A follow-up to #29 (comment).

... I realized that for team members who are not familiar with the 1 hour optimization, not sending a bot reply and Slack notification about it may look like an error, despite it being intentional.

If we're skipping GitHub bot reply because it has been already sent in the past hour, could we send Slack notification about it too, that would include a brief note about why it's being skipped?

So for this situation, on Slack we would see:

[repo] New comment on issue: Test issue by MisRob2
[repo] Bot response skipped on issue: Test issue (less than 1 hour since last bot reply)

Additional benefit is that I will too see that everything is working as expected, and will be able to recognize this scenario easily from when there is an unexpected problem with the action.

Activity

  1. iamshobhraj commented on Jul 23, 2025

    @iamshobhraj
    Contributor

    @MisRob can you assign me this issue

  2. MisRob commented on Jul 24, 2025

    @MisRob
    MemberAuthor

    Assigned, thank you @iamshobhraj

  3. ayushsingh1js commented on Oct 26, 2025

    @ayushsingh1js

    can i solve this issue please assign me

  4. learning-equality-bot commented on Oct 26, 2025

    @learning-equality-bot

    Hi! 👋

    Thanks so much for your interest! This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

    We really appreciate your willingness to help—you're welcome to find a more suitable issue, and let us know if you have any questions. 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions