11# Contributing
22
3- Thanks for your interest in contributing to π Final Form! Please take a moment
4- to review this document ** before submitting a pull request** .
3+ Thanks for your interest in contributing to π Final Form Arrays ! Please take a
4+ moment to review this document ** before submitting a pull request** .
55
66We are open to, and grateful for, any contributions made by the community.
77
88## Reporting issues and asking questions
99
1010Before opening an issue, please search the
11- [ issue tracker] ( https://github.com/erikras/final-form/issues ) to make sure your
12- issue hasnβt already been reported.
11+ [ issue tracker] ( https://github.com/erikras/final-form-arrays /issues ) to make
12+ sure your issue hasnβt already been reported.
1313
1414** We use the issue tracker to keep track of bugs and improvements** to π Final
15- Form itself, its examples, and the documentation. We encourage you to open
16- issues to discuss improvements, architecture, internal implementation, etc. If a
17- topic has been discussed before, we will ask you to join the previous
15+ Form Arrays itself, its examples, and the documentation. We encourage you to
16+ open issues to discuss improvements, architecture, internal implementation, etc.
17+ If a topic has been discussed before, we will ask you to join the previous
1818discussion.
1919
2020For support or usage questions, please search and ask on
21- [ StackOverflow with a ` final-form ` tag] ( https://stackoverflow.com/questions/tagged/final-form ) .
21+ [ StackOverflow with a ` final-form-arrays ` tag] ( https://stackoverflow.com/questions/tagged/final-form-arrays ) .
2222We ask you to do this because StackOverflow has a much better job at keeping
2323popular questions visible. Unfortunately good answers get lost and outdated on
2424GitHub.
@@ -34,8 +34,8 @@ request.**
3434It's never a fun experience to have your pull request declined after investing a
3535lot of time and effort into a new feature. To avoid this from happening, we
3636request that contributors create
37- [ an issue] ( https://github.com/erikras/final-form/issues ) to first discuss any
38- significant new features.
37+ [ an issue] ( https://github.com/erikras/final-form-arrays /issues ) to first discuss
38+ any significant new features.
3939
4040Please try to keep your pull request focused in scope and avoid including
4141unrelated commits.
@@ -74,4 +74,4 @@ npm test
7474```
7575
7676Please ensure that the tests are passing when submitting a pull request. If
77- you're adding new features to π Final Form, please include tests.
77+ you're adding new features to π Final Form Arrays , please include tests.
0 commit comments