-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
add functions to manage user.stats.userCreatedComments #3557
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking good!
Nice one. Same comment about manual testing as the other one. |
@goratt12 Now I've merged in your other branch, I think you've got some fun merge conflicts here now? |
2 flaky tests on run #5670 ↗︎
Details:
settings.spec.ts • 1 flaky test • ci-chrome
howto/comments.spec.ts • 1 flaky test • ci-chrome
Review all test suite changes for PR #3557 ↗︎ |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3557 +/- ##
==========================================
+ Coverage 68.23% 68.32% +0.09%
==========================================
Files 444 445 +1
Lines 13935 13972 +37
Branches 2507 2509 +2
==========================================
+ Hits 9509 9547 +38
+ Misses 4378 4377 -1
Partials 48 48 ☔ View full report in Codecov by Sentry. |
🎉 This PR is included in version 1.183.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 1.185.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR Checklist
PR Type
Description
Using Firebase Functions
Git Issues
Closes #3451
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.