flutter-cherry-pick

To cherry-pick a merged pull request to Flutter stable or beta, provide the PR number or URL to trigger the Dart-based helper script, which validates the PR landed in master and orchestrates the cherry-pick to the target channel.

Cherry-picking to a Flutter candidate branch requires the PR to be landed in master first, and the target branch must match the format flutter-<major>.<minor>-candidate.<hotfix> for stable or beta channels.

You need a cherry-pick workflow for Flutter repositories when landing urgent fixes that have already merged into master and must be backported to stable or beta release channels.

Yes, the Flutter cherry-pick process provides structured guidance for conflict resolution, ensuring an auditable workflow with deterministic steps and clear error handling for common scenarios.

No, you cannot cherry-pick a PR that has not landed in master; the workflow enforces constraints requiring the pull request to be merged into the master branch before any cherry-pick to stable or beta.

Yes, you need Dart because the cherry-pick helper script that validates and orchestrates the backport process is Dart-based, requiring the Dart environment to execute the automation workflow.