zan1456/flutter
1
0
Fork 0
forked from firka/flutter
Code Pull Requests Activity

[Release] Update the cherry-pick process. (#161771)

Browse Source 
Updates to the Flutter cherry-pick process to align with our current
practices. This update:
1. Defaults to automated cherry-picks.
2. Removes the need to create cherry-pick issues.
3. Requires cherry-pick authors to update CHANGELOG.md.

---------

Co-authored-by: Christopher Fujino <christopherfujino@gmail.com>
This commit is contained in:
Kevin Chisholm
2025-01-17 09:44:31 -06:00
committed by GitHub
parent 3297454732
commit bb2d34126c
6 changed files with 32 additions and 111 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/contributing/Design-Documents.md
View File

@@ -2,7 +2,7 @@ If you want to write a design doc for people to review, we recommend using Googl
We have a template you can use, at [flutter.dev/go/template](https://flutter.dev/go/template). It describes the process for minting a `flutter.dev/go/foo` shortlink for your design doc.
We recommend you use that template so that people can immediately recognize that this is a Flutter design document and that it is shared publicly.
After you have created your design doc, the next step is to create a tracking GitHub issue for it. File a new issue to track the design doc using [the design doc issue template](https://github.com/flutter/flutter/issues/new?template=8_design_doc.yml). Assign it to yourself. Add the label "design doc" to the issue.
After you have created your design doc, the next step is to create a tracking GitHub issue for it. File a new issue to track the design doc using [the design doc issue template](https://github.com/flutter/flutter/issues/new?template=7_design_doc.yml). Assign it to yourself. Add the label "design doc" to the issue.
Don't forget to configure your document's Sharing settings so that everyone has comment access. The idea of sharing the document in this way is not necessarily to proactively obtain feedback from the entire community; it is to make it _possible_ for people to share the document with anyone in the community, whether they work for your employer or not, and whether you have personally shared the document with them yet or not.