feat: Add proposal for promote-dependencies-automatically

[zhy76]

What type of PR is this?
/kind feature
/kind documentation

What this PR does / why we need it:
Add proposal for promote-dependencies-automatically

Which issue(s) this PR fixes:
Part of #4036

Special notes for your reviewer:
none
Does this PR introduce a user-facing change?:

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (50b0c51) 52.76% compared to head (4b3d286) 52.79%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4100      +/-   ##
==========================================
+ Coverage   52.76%   52.79%   +0.02%     
==========================================
  Files         239      239              
  Lines       23584    23584              
==========================================
+ Hits        12445    12450       +5     
+ Misses      10462    10458       -4     
+ Partials      677      676       -1     

Flag	Coverage Δ
unittests	52.79% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jwcesign]

/assign

[jwcesign]

/cc @XiShanYongYe-Chang for checking

[karmada-bot]

@jwcesign: GitHub didn't allow me to request PR reviews from the following users: for, checking.

Note that only karmada-io members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @XiShanYongYe-Chang for checking

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/test-infra repository.

[chaunceyjiang]

/assign

[jwcesign]

Hi, @zhy76 Please add the behavior of meeting promoting failure(validation failed or other), and if part dependencies already exist, what should Karmada do?

[zhy76]

Thanks, I will refer to your suggestions~

[jwcesign]

Other lgtm

[jwcesign]

Any more suggestions about port-forward? @chaunceyjiang

[jwcesign]

/cc @chaunceyjiang

Do you have any more suggestions?

[zhy76]

Thanks for your suggestions, I will modify.

[jwcesign]

/cc @XiShanYongYe-Chang

[zhy76]

/approve /批准 /hold /抓住 for setting the approvers and leave final decisions to 用于设置批准者并将最终决定权留给@jwcesign

added, thanks~

[jwcesign]

/approve

Thank you for your excellent work, @zhy76

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jwcesign, RainbowMango

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:

• OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[RainbowMango]

/hold cancel

[RainbowMango]

/lgtm

[RainbowMango]

Pending — Not mergeable. Job e2e test has not succeeded.

I guess the robot missed the e2e test signal. I'll retrigger the tests again.

[RainbowMango]

Pending — Not mergeable. Job e2e test has not succeeded.

I guess the robot missed the e2e test signal. I'll retrigger the tests again.

I'm not sure why the robot hanging there.
Just rebased this PR and try another time.

[RainbowMango]

/lgtm

[zhy76]

Pending — Not mergeable. Job e2e test has not succeeded.

I guess the robot missed the e2e test signal. I'll retrigger the tests again.

I'm not sure why the robot hanging there. Just rebased this PR and try another time.

Thanks~