Closed mrehan27 closed 1 year ago
Pull request title looks good 👍!
If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0
. If this pull request gets merged in, the next release of this project will be 1.0.1
. This pull request is not a breaking change.
All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.
Merging #227 (565bbb9) into main (eb5160a) will decrease coverage by
0.06%
. The diff coverage is0.00%
.
@@ Coverage Diff @@
## main #227 +/- ##
============================================
- Coverage 62.70% 62.64% -0.06%
Complexity 231 231
============================================
Files 94 94
Lines 2145 2147 +2
Branches 281 282 +1
============================================
Hits 1345 1345
- Misses 691 693 +2
Partials 109 109
Impacted Files | Coverage Δ | |
---|---|---|
.../customer/messagingpush/di/DiGraphMessagingPush.kt | 21.42% <0.00%> (-3.58%) |
:arrow_down: |
Build available to test
Version: rehan-push-tracking-opened-SNAPSHOT
Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/
part of: https://github.com/customerio/issues/issues/10211
Changes
PushTrackingUtil
to wrapper SDKs