[flutter_conductor] update dev/tools with release tool#65968
Closed
christopherfujino wants to merge 34 commits intoflutter:masterfrom
Closed
[flutter_conductor] update dev/tools with release tool#65968christopherfujino wants to merge 34 commits intoflutter:masterfrom
christopherfujino wants to merge 34 commits intoflutter:masterfrom
Conversation
00af306 to
b84b776
Compare
This comment has been minimized.
This comment has been minimized.
b84b776 to
bf88f38
Compare
f0c9c4b to
2f4db8b
Compare
Contributor
Author
|
Superceded by https://github.com/flutter/flutter/pull/69791/files to get past CI failures related to flutter tool version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This is a re-write of the
roll_dev.dartscript as a full CLI tool complete with integration tests. At this point, the behavior should be exactly the same asroll_dev.dart. I am putting out a PR at this point so that the actual tool behavior improvements can be reviewed independent of this code re-organization.