-
-
Notifications
You must be signed in to change notification settings - Fork 380
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
Chore/add easy way to test webhooks #3610
Chore/add easy way to test webhooks #3610
Conversation
c0a63b9
to
3c6fcdd
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3610 +/- ##
==========================================
- Coverage 74.23% 67.76% -6.48%
==========================================
Files 41 410 +369
Lines 1246 12693 +11447
Branches 250 2238 +1988
==========================================
+ Hits 925 8601 +7676
- Misses 300 4069 +3769
- Partials 21 23 +2 ☔ View full report in Codecov by Sentry. |
34eff6c
to
729b602
Compare
729b602
to
c076c37
Compare
67ca993
to
9df5c5a
Compare
🎉 This PR is included in version 1.190.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR Checklist
PR Type
Description
This depends on #3598, it probably isn't worth looking at this pull request until that is merged and this is rebased.Introduces an easy way to test webhooks.
A webhook request is made when an how-to is changed to accepted. You can see it in action in the gif below.
This pull request adds a basic nodejs server to the docker-compose and is started when using the emulator. So we can simulate sending webhooks. These changes only affect when the functions are being ran in the emulator.