# Dedupe first-responder Slack notifications \(\#60666\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/da4703be85c81771c37ffbef3d4bc66566c10c7a)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: da4703be85c81771c37ffbef3d4bc66566c10c7a

Requested commit: da4703be85c81771c37ffbef3d4bc66566c10c7a

Commit: da4703be85c81771c37ffbef3d4bc66566c10c7a

Tree: ef245176d3dfe790e95cc55a74d8e4d2ec67658f

Author: Lena

Committer: GitHub

## Message

```
Dedupe first-responder Slack notifications (#60666)

What looks like a single event of applying a few labels is actually
multiple events, and the raciness is racy as we've recently experienced.
One solution would've been adding a “first responders notified” label
for enforcing consistency but issues already have enough labels (and we
could take it off by mistake), so a bot reaction will instead serve as a
marker for any later runs.

So if we're applying multiple labels or changing our mind about, say, an
area label after the notification has already been sent, this should
work fine now, without duplicate notifications.

Release Notes:

- N/A
```

## Parents

- [11d216d8bf3fc33000e5a833d8b5bcf7e581adbb](https://git.cafe/gitcafe/zed/commit/11d216d8bf3fc33000e5a833d8b5bcf7e581adbb?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/da4703be85c81771c37ffbef3d4bc66566c10c7a?format=markdown)