Skip to content

Conversation

@XilaiZhang
Copy link
Contributor

This pull request is opened against a release branch.

To request a cherry pick of a commit, please fill in the form below.
(Questions with an asterisk are required.)

To fill in the form, you can edit this PR description and type your answers after the 'My Answer' keywords.

A flutter domain expert will evaluate this cherry pick request shortly after ALL questions are answered.

  • Issue Link: What is the link to the issue this cherry-pick is addressing?
  My Answer:


  My Answer:


  • Impacted Users: Approximately who will hit this issue (ex. all Flutter devs, Windows developers, all end-customers, apps using X framework feature)?
  My Answer:


  • impact_description: What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)? Does it impact development (ex. flutter doctor crashes when Android Studio is installed), or the shipping production app (the app crashes on launch)
  My Answer:


  • Workaround: Is there a workaround for this issue?
  My Answer:


  • Risk: What is the risk level of this cherry-pick?
  My Answer:
  - [ ] Low
  - [ ] Medium
  - [ ] High

  • Test Coverage: Are you confident that your fix is well-tested by automated tests?
  My Answer:
  - [ ] Yes
  - [ ] No

  • Validation Steps: What are the steps to validate that this fix works?
  My Answer:


* This seems to be unnecessary as users will open a CP PR with the original commit linked in it.
* Add note on changelog description to be less than 80 chars
@XilaiZhang XilaiZhang added the cp: review Cherry-picks in the review queue label Feb 1, 2024
@XilaiZhang
Copy link
Contributor Author

Hello @XilaiZhang! Looks like you attached the cp label and successfully created a cherry pick pr.
Please fill in the information in PR description above, and a release engineer will review this request.

@XilaiZhang
Copy link
Contributor Author

The actor will be whoever triggered the workflow run, not the pr author

@XilaiZhang XilaiZhang closed this Feb 1, 2024
@XilaiZhang XilaiZhang deleted the cp-6 branch February 1, 2024 01:07
auto-submit bot pushed a commit that referenced this pull request Feb 1, 2024
…142676)

Context: Follow up from sync with @itsjustkevin today. Tag and ping the actor of workflow, when the cherry pick pull request is successfully created.

1. actor of workflow will be the username of the user that triggered the initial workflow run. i.e., whoever labels the PR. This person might not necessarily be the author of the cherry pick PR.
2. PR number of newly created cherry pick PR is parsed from the output of "gh pr create" as a multi line string.

Tested: on cp success: #142674 pings the actor of workflow (not the pr author). on cp failure: [example workflow](https://github.com/XilaiZhang/miscellaneous-side-project/actions/runs/7734400373/job/21088324523) leaves a msg on the original PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cp: review Cherry-picks in the review queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants