karmada-io/karmada

AI Summary: This GitHub issue is a request to backport PR #7154 to the `release-1.16`, `release-1.15`, and `release-1.14` branches. It provides clear instructions, a helper script (`hack/cherry_pick_pull.sh`), and documentation links to guide contributors through the cherry-picking process.

AI Summary: This GitHub issue requests the backport of PR #7038 to the `release-1.14`, `release-1.15`, and `release-1.16` branches. It provides clear instructions, a script (`hack/cherry_pick_pull.sh`), and documentation links for performing the cherry-pick, along with guidance on how to assign the task.

AI Summary: This GitHub issue is a request to backport (cherry-pick) PR #7057 to the `release-1.16`, `release-1.15`, and `release-1.14` branches. It provides instructions on how to use a script for the cherry-picking process and links to relevant guidelines for contributors.

AI Summary: This GitHub issue requests the backport (cherry-pick) of PR #6935 to three specific release branches: `release-1.13`, `release-1.14`, and `release-1.15`. The issue provides clear instructions on how to perform the cherry-pick, including the use of an automation script and a detailed guideline, and explains how to assign oneself to the task.

AI Summary: The Karmada Operator API's `HTTPSource` struct has a `URL` field marked as `+required` but also includes `omitempty` in its JSON tag, creating an inconsistency. The task is to remove the `omitempty` tag from the `URL` field's JSON annotation and then regenerate the auto-generated files to ensure the field is always present in serialized JSON.

AI Summary: This GitHub issue is a backport request to cherry-pick PR #6707 into the `release-1.14` and `release-1.13` branches. It provides clear instructions, a script, and relevant documentation for contributors to perform the cherry-pick and assign themselves the task.

AI Summary: This GitHub issue requests the backporting of changes from PR #6674 to three older release branches: `release-1.14`, `release-1.13`, and `release-1.12`. The task involves using a provided script and following detailed guidelines to perform the cherry-pick operation and create new pull requests for each target branch.

AI Summary: This GitHub issue requests the backport of PR #6690 to the `release-1.14` branch. It provides clear instructions, including a script and a link to detailed guidelines, for performing the cherry-pick and creating the new pull request.

AI Summary: This GitHub issue requests the backporting (cherry-picking) of Pull Request #6669. The PR needs to be applied to the `release-1.13` and `release-1.12` branches, following the project's guidelines and using a provided cherry-pick script.

AI Summary: This GitHub issue requests the backporting (cherry-picking) of Pull Request #6544 to specific release branches. The target branches are `release-1.14` and `release-1.13`, with `release-1.12` potentially already addressed. The issue provides clear instructions, a script, and documentation links to guide the contributor through the cherry-picking process.

AI Summary: This GitHub issue requests the backporting of PR #6622 to three specific release branches: `release-1.14`, `release-1.13`, and `release-1.12`. It provides a script (`hack/cherry_pick_pull.sh`) and detailed guidelines to assist contributors in performing the cherry-pick operation.

AI Summary: Cherry-pick the changes from PR #6434 into the appropriate Karmada release branches (1.14, 1.13, and/or 1.12, as determined by the assignee) using the provided `hack/cherry_pick_pull.sh` script. Update the release notes for each new PR created by the script. This involves understanding the Karmada release process and using the provided script and guidelines.

AI Summary: Cherry-pick the changes from PR #6525 into the appropriate Karmada release branches (1.14, 1.13, and 1.12, if necessary). This involves using the provided `hack/cherry_pick_pull.sh` script and updating the release notes for each new PR created.

AI Summary: Cherry-pick the changes from pull request #6491 into the Karmada release-1.14 branch. This involves using the provided `hack/cherry_pick_pull.sh` script to automate the process and then creating a new pull request with release notes copied from the original PR. The decision of whether or not release-1.14 actually needs the patch must be made.