-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
lightning: merge conflict record tables for preprocess duplicate detection and post-import conflict detection (#52307) #52617
lightning: merge conflict record tables for preprocess duplicate detection and post-import conflict detection (#52307) #52617
Conversation
…detection and post-import conflict detection
This reverts commit 9cfd852. revert merge tables
/retest |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-8.1 #52617 +/- ##
================================================
Coverage ? 72.3039%
================================================
Files ? 1467
Lines ? 427165
Branches ? 0
================================================
Hits ? 308857
Misses ? 99022
Partials ? 19286
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
br part lgtm.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger, lance6716, lyzx2001, tangenta The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is an automated cherry-pick of #52307
What problem does this PR solve?
Issue Number: ref #52306
ref #52393
Problem Summary:
What changed and how does it work?
Merge conflict record tables for preprocess duplicate detection and post-import conflict detection.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.