importinto: add doc for conflict resolve
What problem does this PR solve?
Issue Number: ref #60621
Problem Summary:
What changed and how does it work?
Check List
Tests
- [ ] Unit test
- [ ] Integration test
- [ ] Manual test (add detailed scripts or steps below)
- [x] No need to test. ONLY add tech doc
- [x] I checked and no code files have been changed.
Side effects
- [ ] Performance regression: Consumes more CPU
- [ ] Performance regression: Consumes more Memory
- [ ] Breaking backward compatibility
Documentation
- [ ] Affects user behaviors
- [ ] Contains syntax changes
- [ ] Contains variable changes
- [ ] Contains experimental features
- [ ] Changes MySQL compatibility
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.
None
Hi @D3Hunter. Thanks for your PR.
PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/retest
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 68.7466%. Comparing base (dc7e08f) to head (708bb46).
:warning: Report is 7 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #64987 +/- ##
================================================
- Coverage 70.9257% 68.7466% -2.1791%
================================================
Files 1888 1866 -22
Lines 515892 509386 -6506
================================================
- Hits 365900 350186 -15714
- Misses 125576 136878 +11302
+ Partials 24416 22322 -2094
| Flag | Coverage Δ | |
|---|---|---|
| integration | 41.6438% <ø> (-6.5101%) |
:arrow_down: |
| unit | 65.9743% <ø> (+0.3224%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
| Components | Coverage Δ | |
|---|---|---|
| dumpling | 52.8700% <ø> (ø) |
|
| parser | ∅ <ø> (∅) |
|
| br | 39.1471% <ø> (-20.2606%) |
:arrow_down: |
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
/retest
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/retest
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@lance6716 ptal
[LGTM Timeline notifier]
Timeline:
/unhold
/approve
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: D3Hunter, fzzf678, lance6716
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~pkg/disttask/OWNERS~~ [D3Hunter]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.
In response to this:
/retest
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.