-
Kate Lovett authored
I don't know if this is feasible, but figured it was worth seeing. Often times dart fixes are forgotten as part of the code review process. I know some people ignore the PR template, but considered maybe a mention was warranted. I've made the change reflected below:
Unverifiedde97a050
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
PULL_REQUEST_TEMPLATE.md 2.01 KiB
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
- 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, including Features we expect every widget to implement.
- I signed the CLA.
- I listed at least one issue that this PR fixes in the description above.
-
I updated/added relevant documentation (doc comments with
///). - I added new tests to check the change I am making, or this PR is test-exempt.
- I followed the breaking change policy and added Data Driven Fixes where supported.
- All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-new channel on Discord.