Skip to content

chore(ci): if new comment posted on closed item, handle differently#8876

Merged
mikehardy merged 1 commit intomainfrom
@mikehardy/labeler-add-comment-if-closed
Feb 7, 2026
Merged

chore(ci): if new comment posted on closed item, handle differently#8876
mikehardy merged 1 commit intomainfrom
@mikehardy/labeler-add-comment-if-closed

Conversation

@mikehardy
Copy link
Collaborator

@mikehardy mikehardy commented Feb 5, 2026

Description

If a comment is posted on an issue or pull request that is already closed:

  • do not add needs attention label
  • note in a comment that closed items may not receive attention

the state of the issue that created the comment should be available at this property reference per https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=created#issue_comment

I believe this is the correct syntax for a multi-part if: conditional for a workflow step but needs testing live

Test Plan

have to merge this to main then add a comment to an issue or PR that I am OP on - one closed and one open in order to observe behavior

@vercel
Copy link

vercel bot commented Feb 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-native-firebase Ready Ready Preview, Comment Feb 5, 2026 10:42pm

Request Review

@mikehardy mikehardy requested a review from dackers86 February 5, 2026 20:33
@mikehardy mikehardy added the Workflow: Needs Review Pending feedback or review from a maintainer. label Feb 5, 2026
- do not add needs attention label
- note in a comment that closed items may not receive attention
@mikehardy mikehardy merged commit a5bd35e into main Feb 7, 2026
21 checks passed
@mikehardy mikehardy deleted the @mikehardy/labeler-add-comment-if-closed branch February 7, 2026 00:55
@mikehardy mikehardy removed the Workflow: Needs Review Pending feedback or review from a maintainer. label Feb 7, 2026
@mikehardy
Copy link
Collaborator Author

test comment on closed PR

@mikehardy
Copy link
Collaborator Author

a second test comment on closed PR

@InvertaseBot
Copy link
Collaborator

In order to prioritize work in this repository, closed issues and pull requests do not regularly receive attention.

If the underlying issue or pull request still requires attention, opening a new issue with a reproduction
after testing with current versions, or reposting the pull request as a new PR may be the most effective way forward.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants