docs: add pull request and issues template in .github (#5)

* docs: add pull request and issues template in .github

pull request 및 issues 템플릿 추가.

* fix: typo in config.yml

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,32 @@
+---
+name: '🐛Bug'
+about: Report a reproducible bug or regression.
+title: 'Bug: '
+---
+
+<!--
+  Please provide a clear and concise description of what the bug is.
+  Include screenshots if needed.
+-->
+
+## Steps To Reproduce
+
+1.
+1.
+
+<!--
+  Your bug will get fixed much faster if we can run your code.
+  Issues without reproduction steps or code examples may be immediately closed as not actionable.
+-->
+
+Link to code example:
+
+<!--
+  Please provide a CodeSandbox, a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
+  You may provide a screenshot of the application if you think it is relevant to your bug report.
+  Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve.
+-->
+
+## The Current Behavior
+
+## The Expected Behavior

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Contributing Guides📕
+    url: https://github.com/lumirlumir/npm-textlint-rule-allowed-uris?tab=readme-ov-file#contributing
+    about: Contributing Guides for textlint-rule-allowed-uris.
+  - name: Textlint Guides📗
+    url: https://textlint.github.io
+    about: Textlint Guides.
+  - name: AST Tree for textlint📘
+    url: https://textlint.github.io/astexplorer
+    about: AST Tree for textlint.

.github/ISSUE_TEMPLATE/others.md

@@ -0,0 +1,21 @@
+---
+name: '🔧Other Issue'
+about: Report any other issue that does not fit into the predefined categories.
+title: 'Other: '
+---
+
+<!--
+  Please provide a clear and concise description of the issue. Include any relevant details or context.
+-->
+
+## Description
+
+<!--
+  Describe the issue in detail. Include any relevant information or context that might help in understanding the issue.
+-->
+
+## Additional Context
+
+<!--
+  Provide any additional context or details about the issue. This can include links, screenshots, or other relevant information.
+-->

.github/ISSUE_TEMPLATE/suggestion.md

@@ -0,0 +1,34 @@
+---
+name: '💡Suggestion'
+about: Suggest a new feature or improvement.
+title: 'Suggestion: '
+---
+
+<!--
+  Please provide a clear and concise description of your suggestion.
+  Explain the motivation behind it and how it would benefit the project.
+-->
+
+## Description
+
+<!--
+  What is your suggestion? Be detailed and include any relevant information that would help understand the context and benefits.
+-->
+
+## Motivation
+
+<!--
+  Why do you think this suggestion is needed? Describe the problem you are trying to solve or the improvement you would like to see.
+-->
+
+## Proposed Solution
+
+<!--
+  How do you propose to implement this suggestion? If you have ideas on how it can be achieved, please share them here.
+-->
+
+## Additional Context
+
+<!--
+  Add any other context or screenshots about the feature request here.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,40 @@
+<!--
+  Thanks for submitting a pull request!
+  We appreciate you spending the time to work on these changes.
+  Please provide enough information so that others can review your pull request.
+  Before making a pull request, please read our contributing guidelines in `README.md`.
+-->
+
+# Title
+
+<!--
+  Erase `Title` and write down the proper title for this pull request.
+-->
+
+## Summary
+
+<!--
+  Explain the **motivation** for making this change. What existing problem does the pull request solve?
+-->
+
+## Details
+
+<!--
+  Explain the details you made on this pull request.
+  The more detailed it is, the more likely it will be approved.
+-->
+
+## How did you test this change?
+
+<!--
+  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots or videos.
+  How exactly did you verify that your PR solves the issue you wanted to solve?
+  If you leave this empty, your PR will very likely be closed.
+-->
+
+## Resolved Issues
+
+<!--
+  If you fixed problems in issues, write down the numbers of issues.
+  Example: #1, #2, ...
+-->