microsoft
/
react-native-macos
зеркало из https://github.com/microsoft/react-native-macos.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
react-native-macos/.github/ISSUE_TEMPLATE.md

30 строки
1.2 KiB
Markdown
Исходник Обычный вид История

Add dev tools version to new issue template Summary: It's sometimes helpful to provide the Xcode version being used, as in the case of #12795. Closes https://github.com/facebook/react-native/pull/12811 Differential Revision: D4677123 Pulled By: hramos fbshipit-source-id: 28890d1ac65400d4e98ae2eb77e2d7a1a02b9d05
2017-03-09 03:08:32 +03:00
Please read the following carefully before opening a new issue.
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
Your issue may be closed if it does not provide the information required by this template.
Tweak PR and issue templates Reviewed By: mkonicek Differential Revision:D2949403 Ninja: oss-only fb-gh-sync-id: 8e8f68140c833ff8d7c600647dabb52b5ce4d527 shipit-source-id: 8e8f68140c833ff8d7c600647dabb52b5ce4d527
2016-02-18 21:53:41 +03:00
Add dev tools version to new issue template Summary: It's sometimes helpful to provide the Xcode version being used, as in the case of #12795. Closes https://github.com/facebook/react-native/pull/12811 Differential Revision: D4677123 Pulled By: hramos fbshipit-source-id: 28890d1ac65400d4e98ae2eb77e2d7a1a02b9d05
2017-03-09 03:08:32 +03:00
We use GitHub Issues for tracking bugs in React Native.
PR and Issue templates Reviewed By: mkonicek Differential Revision:D2946749 Ninja: GitHub-only fb-gh-sync-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d shipit-source-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d
2016-02-18 02:57:27 +03:00
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
- If you have a question, ask on Stack Overflow: http://stackoverflow.com/questions/tagged/react-native
Add dev tools version to new issue template Summary: It's sometimes helpful to provide the Xcode version being used, as in the case of #12795. Closes https://github.com/facebook/react-native/pull/12811 Differential Revision: D4677123 Pulled By: hramos fbshipit-source-id: 28890d1ac65400d4e98ae2eb77e2d7a1a02b9d05
2017-03-09 03:08:32 +03:00
- If you have a feature request, post it on Canny: https://react-native.canny.io/feature-requests
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
--- Delete everything above this line ---
Tweak bot messages and issue template to make them a bit more friendly Reviewed By: mkonicek Differential Revision:D2951452 Ninja: oss fb-gh-sync-id: a42ee8061e37d7b389fcce0a26a16411b43c1d05 shipit-source-id: a42ee8061e37d7b389fcce0a26a16411b43c1d05
2016-02-19 02:10:14 +03:00
Update the issue template Summary: I notice most people filing issues are ignoring the issue template. I think we should try making it more concise, in particular asking people to provide a rnplay.org reproduction if it is possible. Closes https://github.com/facebook/react-native/pull/10526 Differential Revision: D4070980 Pulled By: hramos fbshipit-source-id: 0781fb9e410d50f8000b6c8cacfd5e5f9e881317
2016-10-25 01:34:23 +03:00
### Description
Tweak bot messages and issue template to make them a bit more friendly Reviewed By: mkonicek Differential Revision:D2951452 Ninja: oss fb-gh-sync-id: a42ee8061e37d7b389fcce0a26a16411b43c1d05 shipit-source-id: a42ee8061e37d7b389fcce0a26a16411b43c1d05
2016-02-19 02:10:14 +03:00
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
Explain what you did, what you expected to happen, and what actually happens.
PR and Issue templates Reviewed By: mkonicek Differential Revision:D2946749 Ninja: GitHub-only fb-gh-sync-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d shipit-source-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d
2016-02-18 02:57:27 +03:00
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
### Reproduction Steps and Sample Code
PR and Issue templates Reviewed By: mkonicek Differential Revision:D2946749 Ninja: GitHub-only fb-gh-sync-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d shipit-source-id: ac8a316ca4c2982a063040d57ddc1f279b81b59d
2016-02-18 02:57:27 +03:00
Update issue template for Sketch -> Snack rename Summary: [We changed the name from Sketch to Snack](https://blog.expo.io/expo-sketch-expo-snack-a444f8dec72b) It's just some text in the issue template :) - Make it clear on the Snack website which version of react-native you are using. Right now we make it possible to pick SDK versions but it's not at all obvious which react-native version that maps to. Closes https://github.com/facebook/react-native/pull/13304 Differential Revision: D4833399 Pulled By: ericvicenti fbshipit-source-id: 25b1fe8b4b1ac7db6737e1ba8f611ad4d8dc3804
2017-04-05 08:01:18 +03:00
Try to reproduce your bug on https://snack.expo.io/ and provide a link.
If you can't reproduce the bug on Snack, provide a sample project. At the very least, provide an example of your code.
Update ISSUE_TEMPLATE.md Summary: Provide a sample new issue template to encourage people to provide additional detail as needed. This should help us reduce the number of new issues that are opened without sufficient information or actionable requests. The minimal use of markdown is intentional, as these guidelines are more likely to be found in raw text inside the [new issue composer](https://github.com/facebook/react-native/issues/new) rather than rendered to HTML. Closes https://github.com/facebook/react-native/pull/9074 Differential Revision: D3785606 Pulled By: hramos fbshipit-source-id: 9982566a0f0d86c71eeface33bd0624a4a9935b2
2016-08-29 20:41:59 +03:00
Ask for solutions in new issue template. Summary: Closes https://github.com/facebook/react-native/pull/10884 Differential Revision: D4167391 Pulled By: hramos fbshipit-source-id: 278b153e9a7bf6975e4d0f23909601f78c8ab3fe
2016-11-11 20:32:35 +03:00
### Solution
Update ISSUE_TEMPLATE.md Summary: Thanks for submitting a PR! Please read these instructions carefully: - [ ] Explain the **motivation** for making this change. - [ ] Provide a **test plan** demonstrating that the code is solid. - [ ] Match the **code formatting** of the rest of the codebase. - [ ] Target the `master` branch, NOT a "stable" branch. What existing problem does the pull request solve? A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI or updates the website. See [What is a Test Plan?][1] to learn more. If you have added code that should be tested, add tests. Sign the [CLA][2], if you haven't already. Small pull requests are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it. Make sure all **tests pass** on both [Travis][3] and [Circle CI][4]. PRs that break tests are unlikely to be merged. Closes https://github.com/facebook/react-native/pull/13122 Differential Revision: D4763115 Pulled By: hramos fbshipit-source-id: 5d4852a133d42e3fd6eb084cf491a672cf075c29
2017-03-23 21:09:07 +03:00
What needs to be done to address this issue? Ideally, provide a pull request with a fix.
Ask for solutions in new issue template. Summary: Closes https://github.com/facebook/react-native/pull/10884 Differential Revision: D4167391 Pulled By: hramos fbshipit-source-id: 278b153e9a7bf6975e4d0f23909601f78c8ab3fe
2016-11-11 20:32:35 +03:00
Update ISSUE_TEMPLATE.md Summary: Provide a sample new issue template to encourage people to provide additional detail as needed. This should help us reduce the number of new issues that are opened without sufficient information or actionable requests. The minimal use of markdown is intentional, as these guidelines are more likely to be found in raw text inside the [new issue composer](https://github.com/facebook/react-native/issues/new) rather than rendered to HTML. Closes https://github.com/facebook/react-native/pull/9074 Differential Revision: D3785606 Pulled By: hramos fbshipit-source-id: 9982566a0f0d86c71eeface33bd0624a4a9935b2
2016-08-29 20:41:59 +03:00
### Additional Information
Update ISSUE_TEMPLATE.md Summary: Some quick copy changes. Closes https://github.com/facebook/react-native/pull/13061 Differential Revision: D4749511 Pulled By: hramos fbshipit-source-id: 5b6f67be40ed071367507ac3c87f7ac67a0584e7
2017-03-22 01:40:04 +03:00
* React Native version: [FILL THIS OUT: Be specific, filling out "latest" here is not enough.]
Update the issue template Summary: I notice most people filing issues are ignoring the issue template. I think we should try making it more concise, in particular asking people to provide a rnplay.org reproduction if it is possible. Closes https://github.com/facebook/react-native/pull/10526 Differential Revision: D4070980 Pulled By: hramos fbshipit-source-id: 0781fb9e410d50f8000b6c8cacfd5e5f9e881317
2016-10-25 01:34:23 +03:00
* Platform: [FILL THIS OUT: iOS, Android, or both?]
Update ISSUE_TEMPLATE.md Summary: Some quick copy changes. Closes https://github.com/facebook/react-native/pull/13061 Differential Revision: D4749511 Pulled By: hramos fbshipit-source-id: 5b6f67be40ed071367507ac3c87f7ac67a0584e7
2017-03-22 01:40:04 +03:00
* Development Operating System: [FILL THIS OUT: Are you developing on MacOS, Linux, or Windows?]
Add dev tools version to new issue template Summary: It's sometimes helpful to provide the Xcode version being used, as in the case of #12795. Closes https://github.com/facebook/react-native/pull/12811 Differential Revision: D4677123 Pulled By: hramos fbshipit-source-id: 28890d1ac65400d4e98ae2eb77e2d7a1a02b9d05
2017-03-09 03:08:32 +03:00
* Dev tools: [FILL THIS OUT: Xcode or Android Studio version, iOS or Android SDK version, if applicable]