@samitouri / QOS-React / commits / 05e487a12f

Add GitHub issue templates (#17815)

Nicolas Gallagher committed Jan 9, 2020 at 16:16 UTC 05e487a12ffee59b75db82995f3f826254444741
5 files changed +113 -27
.github/ISSUE_TEMPLATE.md
+3 -13
@@ -1,14 +1,4 @@
1 -<!--
2 - Note: if the issue is about documentation or the website, please file it at:
3 - https://github.com/reactjs/reactjs.org/issues/new
4 --->
1 +👉 Please follow one of these issue templates:
2 +- https://github.com/facebook/react/issues/new/choose
3
6 -**Do you want to request a *feature* or report a *bug*?**
7 -
8 -**What is the current behavior?**
9 -
10 -**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**
11 -
12 -**What is the expected behavior?**
13 -
14 -**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
4 +Note: to keep the backlog clean and actionable, issues may be immediately closed if they do not follow one of the above issue templates.
.github/ISSUE_TEMPLATE/bug_report.md new
+41
@@ -0,0 +1,41 @@
1 +---
2 +name: "🐛 Bug Report"
3 +about: Report a reproducible bug or regression.
4 +title: 'Bug: '
5 +labels: 'Status: Unconfirmed'
6 +
7 +---
8 +
9 +<!--
10 + Please provide a clear and concise description of what the bug is. Include
11 + screenshots if needed. Please test using the latest version of the relevant
12 + React packages to make sure your issue has not already been fixed.
13 +-->
14 +
15 +React version:
16 +
17 +## Steps To Reproduce
18 +
19 +1.
20 +2.
21 +
22 +<!--
23 + Your bug will get fixed much faster if we can run your code and it doesn't
24 + have dependencies other than React. Issues without reproduction steps or
25 + code examples may be immediately closed as not actionable.
26 +-->
27 +
28 +Link to code example:
29 +
30 +<!--
31 + Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
32 + repository on GitHub, or provide a minimal code example that reproduces the
33 + problem. You may provide a screenshot of the application if you think it is
34 + relevant to your bug report. Here are some tips for providing a minimal
35 + example: https://stackoverflow.com/help/mcve.
36 +-->
37 +
38 +## The current behavior
39 +
40 +
41 +## The expected behavior
.github/ISSUE_TEMPLATE/documentation.md new
+13
@@ -0,0 +1,13 @@
1 +---
2 +name: "📃 Documentation Issue"
3 +about: This issue tracker is not for documentation issues. Please file documentation issues at https://github.com/reactjs/reactjs.org.
4 +title: 'Docs: '
5 +labels: 'Resolution: Invalid'
6 +
7 +---
8 +
9 +🚨 This issue tracker is not for documentation issues. 🚨
10 +
11 +The React website is hosted on a separate repository. You may let the
12 +team know about any issues with the documentation by opening an issue there:
13 +- https://github.com/reactjs/reactjs.org/issues/new
.github/ISSUE_TEMPLATE/question.md new
+29
@@ -0,0 +1,29 @@
1 +---
2 +name: "🤔 Questions and Help"
3 +about: This issue tracker is not for questions. Please ask questions at https://stackoverflow.com/questions/tagged/react.
4 +title: 'Question: '
5 +labels: 'Resolution: Invalid', 'Type: Question'
6 +
7 +---
8 +
9 +🚨 This issue tracker is not for questions. 🚨
10 +
11 +As it happens, support requests that are created as issues are likely to be closed. We want to make sure you are able to find the help you seek. Please take a look at the following resources.
12 +
13 +## Coding Questions
14 +
15 +### https://stackoverflow.com/questions/tagged/react
16 +
17 +If you have a coding question related to React and React DOM, it might be better suited for Stack Overflow. It's a great place to browse through frequent questions about using React, as well as ask for help with specific questions.
18 +
19 +## Talk to other React developers
20 +
21 +### https://www.reactiflux.com/
22 +
23 +Reactiflux is an active community of React and React Native developers. If you are looking for immediate assistance or have a general question about React, the #help-react channel is a good place to start.
24 +
25 +## Proposals
26 +
27 +### https://github.com/reactjs/rfcs
28 +
29 +If you'd like to discuss topics related to the future of React, or would like to propose a new feature or change before sending a pull request, please check out the discussions and proposals repository.
.github/PULL_REQUEST_TEMPLATE.md
+27 -14
@@ -1,14 +1,27 @@
1 -**Before submitting a pull request,** please make sure the following is done:
2 -
3 -1. Fork [the repository](https://github.com/facebook/react) and create your branch from `master`.
4 -2. Run `yarn` in the repository root.
5 -3. If you've fixed a bug or added code that should be tested, add tests!
6 -4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
7 -5. Run `yarn test-prod` to test in the production environment. It supports the same options as `yarn test`.
8 -6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
9 -7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
10 -8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
11 -9. Run the [Flow](https://flowtype.org/) typechecks (`yarn flow`).
12 -10. If you haven't already, complete the CLA.
13 -
14 -**Learn more about contributing:** https://reactjs.org/docs/how-to-contribute.html
1 +<!--
2 + Thanks for submitting a pull request!
3 + We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.
4 +
5 + Before submitting a pull request, please make sure the following is done:
6 +
7 + 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `master`.
8 + 2. Run `yarn` in the repository root.
9 + 3. If you've fixed a bug or added code that should be tested, add tests!
10 + 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
11 + 5. Run `yarn test-prod` to test in the production environment. It supports the same options as `yarn test`.
12 + 6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
13 + 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
14 + 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
15 + 9. Run the [Flow](https://flowtype.org/) typechecks (`yarn flow`).
16 + 10. If you haven't already, complete the CLA.
17 +
18 + Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
19 +-->
20 +
21 +## Summary
22 +
23 +<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
24 +
25 +## Test Plan
26 +
27 +<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. -->