Is your feature request related to a problem? Please describe.
We have a slack channel that's relatively low volume, but has notifications for open PRs for a repo.
A notification arrives, letting us know there's a stale dependency:
Oh good, let's approve that PR and keep up to date. Lovely.
But the message lurks around -- it's now wrong, misleading to anyone who sees it. The problem's resolved, but Slack doesn't reflect that. Non-administrators can't delete it. And because it's low volume, it's not uncommon that the last handful of messages are these sorts of notifications.
Describe the solution you'd like
The state of the open PR list is automatically edited to reflect changes. This might range from crossing out / marking the merged commits as merged if it's considered that it's important that the notification continues to exist (as text might refer to it), or deleting items from the notification (or the notification itself) if that's considered acceptable. (This might need to be a config option, I imagine different companies might have different needs.)
Describe alternatives you've considered
We could move this to another channel, but that decreases visibility of the initial alert, and it's here because the people who should respond to it are here. This doesn't fix the "stale info" issue.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. We have a slack channel that's relatively low volume, but has notifications for open PRs for a repo.
A notification arrives, letting us know there's a stale dependency:
Oh good, let's approve that PR and keep up to date. Lovely. But the message lurks around -- it's now wrong, misleading to anyone who sees it. The problem's resolved, but Slack doesn't reflect that. Non-administrators can't delete it. And because it's low volume, it's not uncommon that the last handful of messages are these sorts of notifications.
Describe the solution you'd like The state of the open PR list is automatically edited to reflect changes. This might range from crossing out / marking the merged commits as merged if it's considered that it's important that the notification continues to exist (as text might refer to it), or deleting items from the notification (or the notification itself) if that's considered acceptable. (This might need to be a config option, I imagine different companies might have different needs.)
Describe alternatives you've considered We could move this to another channel, but that decreases visibility of the initial alert, and it's here because the people who should respond to it are here. This doesn't fix the "stale info" issue.
Additional context Add any other context or screenshots about the feature request here.