-
-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move discord webhook logic to seperate file #3636
base: master
Are you sure you want to change the base?
Conversation
Encountered Github automatic secret push block, resolved it by these steps: |
there are some conflicts. (probably due to the vite migration, sorry!) |
1 flaky test on run #5863 ↗︎
Details:
src/integration/howto/read.spec.ts • 1 flaky test • ci-chrome
Review all test suite changes for PR #3636 ↗︎ |
Seen the error @goratt12? Looks relevant. |
Yeah I don't know how I missed it, fixed it now. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3636 +/- ##
==========================================
+ Coverage 73.68% 74.71% +1.03%
==========================================
Files 41 44 +3
Lines 1254 1317 +63
Branches 253 268 +15
==========================================
+ Hits 924 984 +60
- Misses 308 311 +3
Partials 22 22 ☔ View full report in Codecov by Sentry. |
PR Checklist
PR Type
Description
** tested and working **
Refactored the notification logic by keeping only the Discord notification handling in
firebase-discord.ts
file. ThenotifyPinAccepted
andnotifyHowToAccepted
functions have been separated into their respective files,mapPinUpdates/index.ts
andhowtoUpdates/index.ts
.Git Issues
Closes #
Screenshots/Videos
If useful, provide screenshot or capture to highlight main changes
What happens next?
Thanks for the contribution! We try to make sure all PRs are reviewed ahead of our monthly maintainers call (first Monday of the month)
If the PR is working as intended it'll be merged and included in the next platform release, if not changes will be requested and re-reviewed once updated.
If you need more immediate feedback you can try reaching out on Discord in the Community Platform
development
channel.