···33about: Create a report to help us improve
44title: ''
55labels: "bug \U0001F41B"
66-assignees: ''
77-88----
66+---<!--
77+ Please describe your bug clearly and concisely.
88+ Include a screenshot or a reproduction to illustrate
99+ the bug and how to reproduce it.
1010+ Please also leave a note on what version of urql you're using
1111+ and include a list of exchanges (if any).
1212+-->
9131010-**Describe the bug**
1111-A clear and concise description of what the bug is.
1414+urql version & exchanges:
12151316**Steps to reproduce**
1414-Steps to reproduce the behavior:
1515-1. Go to '...'
1616-2. Click on '....'
1717-3. Scroll down to '....'
1818-4. See error
1717+1818+1. 2.
19192020**Expected behavior**
2121-A clear and concise description of what you expected to happen.
22212322**Actual behavior**
2424-A clear and concise description of what is actually happening.
25232626-**Additional context**
2727-Add any other context about the problem here.
2828-2929-It offers a lot of help when you add a reproduction to your bug report, here are some templates to help you get started:
3030-3131-- client: https://codesandbox.io/s/urql-issue-template-client-iui0o
3232-- server: https://codesandbox.io/s/urql-issue-template-server-0ufyz
2424+<!--
2525+ Your issue will be addressed much faster if you include a
2626+ reproduction. Here are some templates to help you create one:
2727+ - client: https://codesandbox.io/s/urql-issue-template-client-iui0o
2828+ - server: https://codesandbox.io/s/urql-issue-template-server-0ufyz
2929+-->
+21
.github/ISSUE_TEMPLATE/question.md
···11+---
22+name: '🤔 Questions and Help'
33+about: Create a thread to ask your questions
44+title: ''
55+labels: "question \U0001F64B"
66+---<!--
77+ 🚨 The issue tracker is not great for getting help!
88+ If you have a usage question, maybe consider asking
99+ for help on our Spectrum:
1010+ https://spectrum.chat/urql
1111+1212+ If you'd like to go ahead remember to answer:
1313+ - What problem are you running into?
1414+ - What do you think may it be related to?
1515+ - Is this covered in the docs?
1616+1717+ Please also leave a note on what version of urql you're using
1818+ and include a list of exchanges (if any).
1919+-->
2020+2121+urql version & exchanges:
+22
.github/PULL_REQUEST_TEMPLATE.md
···11+<!--
22+ Thanks for opening a pull request! We appreciate your dedication and help!
33+ Before submitting your pull request, please make sure to read our CONTRIBUTING guide.
44+55+ The best contribution is always a PR! However, if you're starting to work on a large
66+ change, it's best to make sure to open an issue first.
77+88+ If this PR is already related to an issue, please reference it like so:
99+ Resolves #123
1010+-->
1111+1212+## Summary
1313+1414+<!-- What's the motivation of this change? What does it solve? -->
1515+1616+## Set of changes
1717+1818+<!--
1919+ Roughly list the changes you've made and which packages are affected.
2020+ Leave some notes on what may be noteworthy files you've changed.
2121+ And lastly, please let us know if you think this is a breaking change.
2222+-->