Showing
1 changed file
with
3 additions
and
1 deletions
| @@ -28,8 +28,10 @@ Alternatively, you can also use `git pull-request` via [GitHub hub](https://hub. | @@ -28,8 +28,10 @@ Alternatively, you can also use `git pull-request` via [GitHub hub](https://hub. | ||
| 28 | 28 | ||
| 29 | # Notes | 29 | # Notes |
| 30 | 30 | ||
| 31 | - * You should remember to exlcude all files and directories your IDE might generate using the `.gitignore` files (if they do not already contain them for your IDE). | 31 | + * You should remember to exclude all files and directories your IDE might generate using the `.gitignore` files (if they do not already contain them for your IDE). |
| 32 | If you feel like you can make useful additions to any of the `.gitignore` files, you can include them in your pull request, potentially with an explanation. | 32 | If you feel like you can make useful additions to any of the `.gitignore` files, you can include them in your pull request, potentially with an explanation. |
| 33 | 33 | ||
| 34 | * It is probably easier for you to run the integration tests for the plugin locally using `flutter drive --target=test_driver/app.dart` in the `example` directory before opening a pull request (CI also runs the integration tests). | 34 | * It is probably easier for you to run the integration tests for the plugin locally using `flutter drive --target=test_driver/app.dart` in the `example` directory before opening a pull request (CI also runs the integration tests). |
| 35 | This way you can ensure that any changes you have made work properly. Furthermore, you might also want to add some tests if you implement new functionality. | 35 | This way you can ensure that any changes you have made work properly. Furthermore, you might also want to add some tests if you implement new functionality. |
| 36 | + | ||
| 37 | + * You should also run `flutter format . --fix` in the root directory and make sure that `flutter analyze` does not report any errors. |
-
Please register or login to post a comment