Update PULL_REQUEST_TEMPLATE.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -8,7 +8,7 @@
 
 - [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
 - [ ] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
-- [ ] I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides].
+- [ ] I read and followed the [Flutter Style Guide] and the [C++, Objective-C, Java style guides]. (Note that unlike the flutter/flutter repo, we do use dart formatter in the flutter/plugins repo. See [plugin_tool format](../script/tool/README.md#format-code))
 - [ ] I signed the [CLA].
 - [ ] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. `[shared_preferences]`
 - [ ] I listed at least one issue that this PR fixes in the description above.

CONTRIBUTING.md

@@ -48,6 +48,14 @@ for any of the following plugins, we encourage you to submit it
    fetch from the master repository, not your clone, when running `git fetch`
    et al.)
 
+
+## Setting up tools
+
+
+We use a range of tooling script to do varies of things on CI. (testing, formatting, etc.)
+Your are likely to use some of the tooling script locally in your contributing journey.
+See [plugin_tools](./script/tool/README.MD) for more details
+
 ## Running the examples
 
 
@@ -137,13 +145,7 @@ pod lib lint --allow-warnings
 XCUITests aren't usually configured with cocoapods in this repo. They are configured in a xcode workspace target named RunnerUITests.
 To run all the XCUITests in a plugin, follow the steps in a regular iOS development workflow [here](https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/05-running_tests.html)
 
-For convenience, a [flutter_plugin_tools](https://pub.dev/packages/flutter_plugin_tools) command `xctest` could also be used to run all the XCUITests in the repo:
-
-```console
-pub global activate flutter_plugin_tools
-cd <path_to_plugins>/packages
-pub global run flutter_plugin_tools xctest --target RunnerUITests --skip <plugins_to_skip>
-```
+For convenience, a [plugin_tools](./script/tool/README.MD) command [xctest](./script/tool/README.MD#run-xctests) could also be used to run all the XCUITests in the repo.
 
 ## Contributing code
 
@@ -159,12 +161,12 @@ To start working on a patch:
  * `git fetch upstream`
  * `git checkout upstream/master -b <name_of_your_branch>`
  * Hack away.
- * Verify changes with [flutter_plugin_tools](https://pub.dev/packages/flutter_plugin_tools)
+ * Verify changes with [plugin_tools](./script/tool/README.MD).
 ```
-pub global activate flutter_plugin_tools
-pub global run flutter_plugin_tools format --plugins plugin_name
-pub global run flutter_plugin_tools analyze --plugins plugin_name
-pub global run flutter_plugin_tools test --plugins plugin_name
+$ cd script/tool & pub get
+$ dart run ./script/tool/lib/src/main.dart format --plugins plugin_name
+$ pub run ./script/tool/lib/src/main.dart analyze --plugins plugin_name
+$ pub run ./script/tool/lib/src/main.dart test --plugins plugin_name
 ```
  * `git commit -a -m "<your informative commit message>"`
  * `git push origin <name_of_your_branch>`
@@ -245,37 +247,4 @@ Releasing a package is a two-step process.
    done manually with `git tag $tagname && git push upstream $tagname` while
    checked out on the commit that updated `version` in `pubspec.yaml`.
 
-We've recently updated
-[flutter_plugin_tools](https://github.com/flutter/plugin_tools) to wrap both of
-those steps into one command to make it a little easier. This new tool is
-experimental. Feel free to fall back on manually running `pub publish` and
-creating and pushing the tag in git if there are issues with it.
-
-Install the tool by running:
-
-```terminal
-$ pub global activate flutter_plugin_tools
-```
-
-Then, from the root of your local `flutter/plugins` repo, use the tool to
-publish a release.
-
-```terminal
-$ pub global run flutter_plugin_tools publish-plugin --package $package
-```
-
-By default the tool tries to push tags to the `upstream` remote, but that and
-some additional settings can be configured. Run `pub global activate
-flutter_plugin_tools --help` for more usage information.
-
-The tool wraps `pub publish` for pushing the package to pub, and then will
-automatically use git to try and create and push tags. It has some additional
-safety checking around `pub publish` too. By default `pub publish` publishes
-_everything_, including untracked or uncommitted files in version control.
-`flutter_plugin_tools publish-plugin` will first check the status of the local
-directory and refuse to publish if there are any mismatched files with version
-control present.
-
-There is a lot about this process that is still to be desired. Some top level
-items are being tracked in
-[flutter/flutter#27258](https://github.com/flutter/flutter/issues/27258).
+For convenience, a [publish-plugin](./script/tool/README.MD#publish-and-tag-release) tool script could be used to do both step at once.

script/tool/README.md

@@ -1,8 +1,60 @@
 # Flutter Plugin Tools
 
+Note: The commands in tools are designed to run under plugins/ or plugins/packages/.
+
 To run the tool:
 
 ```sh
 dart pub get
 dart run lib/src/main.dart <args>
 ```
+
+## Format Code
+
+```sh
+cd <path_to_plugins>/packages
+dart run ./script/tool/lib/src/main.dart format --plugins plugin_name
+```
+
+## Run static analyzer
+
+```sh
+cd <path_to_plugins>/packages
+pub run ./script/tool/lib/src/main.dart analyze --plugins plugin_name
+```
+
+## Run dart unit tests
+
+```sh
+cd <path_to_plugins>/packages
+pub run ./script/tool/lib/src/main.dart test --plugins plugin_name
+```
+
+## Run XCTests
+
+```sh
+cd <path_to_plugins>/packages
+dart run lib/src/main.dart xctest --target RunnerUITests --skip <plugins_to_skip>
+```
+
+## Publish and tag release
+
+``sh
+cd <path_to_plugins>/packages
+dart run ./script/tool/lib/src/main.dart publish-plugin --package $package
+``
+
+By default the tool tries to push tags to the `upstream` remote, but that and
+some additional settings can be configured. Run `dart run ./script/tool/lib/src/main.dart publish-plugin --help` for more usage information.
+
+The tool wraps `pub publish` for pushing the package to pub, and then will
+automatically use git to try and create and push tags. It has some additional
+safety checking around `pub publish` too. By default `pub publish` publishes
+_everything_, including untracked or uncommitted files in version control.
+`publish-plugin` will first check the status of the local
+directory and refuse to publish if there are any mismatched files with version
+control present.
+
+There is a lot about this process that is still to be desired. Some top level
+items are being tracked in
+[flutter/flutter#27258](https://github.com/flutter/flutter/issues/27258).