Skip to content
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.

fix: get the thread autoresponding working #12

Merged
merged 2 commits into from
Jun 7, 2024
Merged

fix: get the thread autoresponding working #12

merged 2 commits into from
Jun 7, 2024

Conversation

naomi-lgbt
Copy link
Collaborator

Pull Request

Description:

Related Issue:

Closes #XXXXX

jpvajda and others added 2 commits May 24, 2024 10:22
* updates sticky message

* resolves failed lint check
@lukeocodes lukeocodes changed the base branch from main to staging June 7, 2024 08:38
@lukeocodes lukeocodes merged commit 6ee914e into deepgram-devs:staging Jun 7, 2024
5 checks passed
lukeocodes added a commit that referenced this pull request Jun 7, 2024
* feat: adding event listeners for relevant events (#8)

* feat: adding event listeners for relevant events

* feat: adding event listeners for relevant events

---------

Co-authored-by: Vaibhav Rai <[email protected]>

* Refactor: Make error handling rock solid (#10)

* fix: get the thread autoresponding working (#12)

* updates sticky message (#11)

* updates sticky message

* resolves failed lint check

* fix: get the thread autoresponding working

---------

Co-authored-by: John Vajda (JV) <[email protected]>

* fix: suppress errors when fetching sticky (#13)

* updates sticky message (#11)

* updates sticky message

* resolves failed lint check

* fix: suppress errors when fetching sticky

We don't need to care if the sticky message got deleted some other
way. As such, failing to fetch the message should not bubble up
and block the process. So we can swallow those errors and
proceed with the rest of the logic.

---------

Co-authored-by: John Vajda (JV) <[email protected]>

---------

Co-authored-by: Vaibhav Rai <[email protected]>
Co-authored-by: Naomi <[email protected]>
Co-authored-by: John Vajda (JV) <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants