Skip to content

Commit 3c30af9

Browse files
hramosM-i-k-e-l
authored andcommitted
(CONTRIBUTING.md) Link to Issues wiki (facebook#25035)
Summary: Link to https://github.com/facebook/react-native/wiki/Issues ## Changelog [Internal] [Changed] - Link to Issues wiki Pull Request resolved: facebook#25035 Differential Revision: D15516862 Pulled By: cpojer fbshipit-source-id: 2f70a28685852293f946c0b1128184226d56aaa7
1 parent 5a85f44 commit 3c30af9

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

CONTRIBUTING.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ If you are eager to start contributing code right away, we have a list of [good
1818

1919
There are other ways you can contribute without writing a single line of code. Here are a few things you can do to help out:
2020

21-
1. **Replying and handling open issues.** We get a lot of issues every day, and some of them may lack necessary information. You can help out by guiding people through the process of filling out the issue template, asking for clarifying information, or pointing them to existing issues that match their description of the problem. We'll cover more about this process later, in [Handling Issues](http://github.com/facebook/react-native/wiki/Handling-Issues).
21+
1. **Replying and handling open issues.** We get a lot of issues every day, and some of them may lack necessary information. You can help out by guiding people through the process of filling out the issue template, asking for clarifying information, or pointing them to existing issues that match their description of the problem. We cover more about this process in the [Issue Triage wiki](https://github.com/facebook/react-native/wiki/Issues#triage).
2222
2. **Reviewing pull requests for the docs.** Reviewing [documentation updates](https://github.com/facebook/react-native-website/pulls) can be as simple as checking for spelling and grammar. If you encounter situations that can be explained better in the docs, click **Edit** at the top of most docs pages to get started with your own contribution.
2323
3. **Help people write test plans.** Some pull requests sent to the main repository may lack a proper test plan. These help reviewers understand how the change was tested, and can speed up the time it takes for a contribution to be accepted.
2424

@@ -30,6 +30,7 @@ We use GitHub issues and pull requests to keep track of bug reports and contribu
3030

3131
You can learn more about the contribution process in the following documents:
3232

33+
* [Issues](https://github.com/facebook/react-native/wiki/Issues)
3334
* [Pull Requests](https://github.com/facebook/react-native/wiki/Pull-Requests)
3435

3536
We also have a thriving community of contributors who would be happy to help you get set up. You can reach out to us through [@ReactNative](http://twitter.com/reactnative) (the React Native team) and [@ReactNativeComm](http://twitter.com/reactnativecomm) (the React Native Community organization).
@@ -47,9 +48,9 @@ There are a few other repositories you might want to familiarize yourself with:
4748

4849
Browsing through these repositories should provide some insight into how the React Native open source project is managed.
4950

50-
## Handling Issues
51+
## GitHub Issues
5152

52-
We use GitHub issues to track bugs exclusively. You can report an issue by filing a [Bug Report](https://github.com/facebook/react-native/issues/new/choose). Watch this space for more details on how to get involved and triage issues.
53+
We use GitHub issues to track bugs exclusively. We have documented our issue handling processes in the [Issues wiki](https://github.com/facebook/react-native/wiki/Issues).
5354

5455
### Security Bugs
5556

0 commit comments

Comments
 (0)