NoRedInk/noredink-ui
1
1
Fork 0
mirror of https://github.com/NoRedInk/noredink-ui.git synced 2025-01-06 22:49:38 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix typo in PR template

Browse Source
This commit is contained in:
Brian Hicks 2023-03-28 17:21:53 -05:00
parent 756a4640fc
commit 42f8d3d066
No known key found for this signature in database
GPG Key ID: C4F324B9CAAB0D50
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/pull_request_template.md vendored
View File

@ -58,7 +58,7 @@ Please link to any relevant context and stories.
- if you want to test the component directly, add tests under `tests/Spec`. Historically, this has been the more popular Elm testing strategy for noredink-ui.
- [ ] Component API follows standard patterns in noredink-ui
- e.g., as a dev, I can conveniently add an `nriDescription`
- and adding a new feature to the component will _not_ require major API changes to the comopnent
- and adding a new feature to the component will _not_ require major API changes to the component
- [ ] Please assign [team-accessibilibats-a11ybats](https://github.com/orgs/NoRedInk/teams/team-accessibilibats-a11ybats) as a reviewer in addition to assigning a reviewer from your team
@ -94,4 +94,4 @@ Please link to any relevant context and stories.
- [ ] Changes to the component are tested/the new version of the component is tested
- [ ] Component API follows standard patterns in noredink-ui
- e.g., as a dev, I can conveniently add an `nriDescription`
- and adding a new feature to the component will _not_ require major API changes to the comopnent
- and adding a new feature to the component will _not_ require major API changes to the component