Skip to content

Commit eca7d6e

Browse files
author
Chris Yang
authored
fix MD (flutter#3815)
1 parent d572371 commit eca7d6e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ for any of the following plugins, we encourage you to submit it
4949
## Setting up tools
5050

5151
There are scripts for many common tasks (testing, formatting, etc.) that will likely be useful in preparing a PR.
52-
See [plugin_tools](./script/tool/README.MD) for more details.
52+
See [plugin_tools](./script/tool/README.md) for more details.
5353

5454
## Running the examples
5555

@@ -139,7 +139,7 @@ pod lib lint --allow-warnings
139139
XCUITests aren't usually configured with cocoapods in this repo. They are configured in a xcode workspace target named RunnerUITests.
140140
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)
141141

142-
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.
142+
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.
143143

144144
## Contributing code
145145

@@ -155,7 +155,7 @@ To start working on a patch:
155155
* `git fetch upstream`
156156
* `git checkout upstream/master -b <name_of_your_branch>`
157157
* Hack away.
158-
* Verify changes with [plugin_tools](./script/tool/README.MD).
158+
* Verify changes with [plugin_tools](./script/tool/README.md).
159159
```sh
160160
cd script/tool && pub get && cd ../../
161161
dart ./script/tool/lib/src/main.dart format --plugins plugin_name
@@ -231,7 +231,7 @@ Some things to keep in mind before publishing the release:
231231
from people that immediately adopt it, and uncovering and resolving those
232232
support issues will take more time if you're unavailable.
233233

234-
To release a package, a [publish-plugin](./script/tool/README.MD#publish-and-tag-release) tool script should be used. This command publishes the new version to pub.dev, and tags the commit in the format of `<package_name>-v<package_version>` then pushes it to upstream.
234+
To release a package, a [publish-plugin](./script/tool/README.md#publish-and-tag-release) tool script should be used. This command publishes the new version to pub.dev, and tags the commit in the format of `<package_name>-v<package_version>` then pushes it to upstream.
235235

236236
Alternatively, one can release a package in the below 2-step process.
237237

0 commit comments

Comments
 (0)