Merge pull request #20 from madeiramadeirabr/feat/arquivos_git

Atualização de arquivos voltados para a comunidade e gestão do projeto.

Author: andersoncontreira

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,45 +1,67 @@
 ---
-name: Bug reports
-about: Bug reports
-title: bug - [component/module] - bug title
-labels: ''
-assignees: ''
+name: Bug Report
+about: File a bug report
+title: "bug - [component/module] - bug title"
+labels: "bug report"
+assignees: ""
 ---
 
-<!-- ## We appreciate you creating a new issue 😄!
+## Thanks for creating an issue 😄!
 
-Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
-Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
+Please search open/closed issues before submitting. Someone might have asked the same thing before.
+To help us, please take the time to accurately fill out this template. ❤️
 
--->
+#### 1. Describe the bug:
 
-#### 1. Bug description:
+> A brief description of the issue.
+> Ex: When I \_**\_, I expected \_\_** to happen but \_\_\_\_ happened instead.
 
-> Enter a simple description about the bug
-> Example: When I \_**\_, I expected the behavior \_\_** but the behavior \_\_\_\_ occurred
+---
+
+#### 2. Version:
+
+> The version of this library that are using.
 
 ---
 
-#### 3. Link to bug example:
+#### 3. Link to Reproduction:
 
-> Link to CodeSandbox or any sandbox service that shows the error happening (see https://github.com/accezar/multi-package-start#codesandbox-templates for examples)
+> A link to a CodeSandbox or any other sandbox service which demonstrates the bug (see https://github.com/accezar/multi-package-start#codesandbox-templates for templates)
 
 ---
 
-#### 4. Step-by-step to reproduces the error behavior:
+#### 4. Steps to reproduce
 
 > 1. Go to '...'
 > 2. Click on '....'
-> 3. Get the error
+> 3. Scroll down to '....'
+> 4. See error
 
 ---
 
 #### 5. Screenshots
 
-> Se possível, adicione screenshots para ajudar a explicar o erro
+> If applicable, add screenshots to help explain your problem.
+
+---
+
+#### 6. Desktop (please complete the following information):
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+---
+
+#### 7. Smartphone (please complete the following information):
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 ---
 
-#### 6. Extra info
+#### 8. Additional context
 
-> Add any additional information here that you think is relevant to understanding the issue
+> Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,75 @@
+name: "Bug Report"
+description: "File a bug report"
+labels: ["bug report"]
+body:
+  - type: "markdown"
+    attributes:
+      value: |
+        Thanks for creating an issue 😄!
+
+        Please search open/closed issues before submitting. Someone
+        might have asked the same thing before 😉!
+
+        We're all volunteers here, so help us help you by taking the time to
+        accurately fill out this template. ❤️
+  - type: "input"
+    id: "description"
+    attributes:
+      label: "Description"
+      description: "A brief description of the issue."
+      placeholder: |
+        When I ____, I expected ____ to happen but ____ happened instead.
+    validations:
+      required: true
+  - type: "input"
+    id: "reproduction"
+    attributes:
+      label: "Link to Reproduction"
+      description: |
+        A link to a env reproduction which demonstrates the bug (see
+        https://github.com/accezar/multi-package-start/#codesandbox-templates for
+        templates)
+      placeholder: "https://codesandbox.io/"
+    validations:
+      required: true
+  - type: "textarea"
+    id: "steps"
+    attributes:
+      label: "Steps to reproduce"
+      description: |
+        Explain how to cause the issue in the provided reproduction.
+      value: |
+        1. Go to '...'
+        2. Click on '...'
+        3. Scroll down to '...'
+        4. See error
+  - type: "input"
+    id: "lib-version"
+    attributes:
+      label: "Library Version"
+      description: "The version of lib you use."
+      placeholder: "0.0.0"
+    validations:
+      required: true
+  - type: "input"
+    id: "browser"
+    attributes:
+      label: "Browser"
+      description: "The browser(s) this issue occurred with."
+      placeholder: "Google Chrome 93"
+  - type: "checkboxes"
+    id: "operating-system"
+    attributes:
+      label: "Operating System"
+      description: "The operating system(s) this issue occurred with."
+      options:
+        - label: "macOS"
+        - label: "Windows"
+        - label: "Linux"
+  - type: "textarea"
+    id: "additional-information"
+    attributes:
+      label: "Additional Information"
+      description: |
+        Use this section to provide any additional information you might have
+        like screenshots, notes, or links to ideas.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/documentation-request.md

@@ -0,0 +1,25 @@
+---
+name: Documentation Request
+about: Request for documentation to be added/altered
+title: "doc - [component] - request title"
+labels: "documentation request"
+assignees: ""
+---
+
+## Thanks for filing a documentation request 📚!
+
+If you have an idea for a new documentation topic, noticed that something is not properly documented, or feel that something is incorrect with the current documentation, you're in the right place!
+
+#### 1. Subject:
+
+What is the subject (component, function, topic) of this request?
+
+> Ex: RadioGroup
+
+---
+
+#### 2. Description:
+
+What about the subject's documentation should be added or changed?
+
+> Ex: Add a usage example of RadioGroup in action

.github/ISSUE_TEMPLATE/documentation_request.md

@@ -0,0 +1,28 @@
+name: "Documentation Request"
+description: "Request for documentation to be added/altered"
+labels: ["needs triage", "Topic: Documentation 📚"]
+body:
+  - type: "markdown"
+    attributes:
+      value: |
+        Thanks for filing a documentation request 📚!
+
+        If you have an idea for a new documentation topic, noticed that
+        something is not properly documented, or feel that something is
+        incorrect with the current documentation, you're in the right place!
+  - type: "input"
+    id: "subject"
+    attributes:
+      label: "Subject"
+      description: "What is the subject (component, function, topic) of this request?"
+      placeholder: "RadioGroup"
+    validations:
+      required: true
+  - type: "textarea"
+    id: "description"
+    attributes:
+      label: "Description"
+      description: "What about the subject's documentation should be added or changed?"
+      placeholder: "Add a usage example of RadioGroup in action"
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/documentation_request.yml

@@ -1,42 +1,51 @@
 ---
-name: Feature request
-about: Request a new feature or improvement
-title: feat - [component/context] - request title
-labels: enhancement
-assignees: ''
+name: Feature Request
+about: Request a feature or enhancement
+title: "feat - [component/context] - feature request title"
+labels: "feature requested"
+assignees: ""
 ---
 
-<!-- ## Thank you for creating a request 😄!
+## Thanks for filing an issue 😄!
 
-Don't forget to check that there are no other open/closed issues before creating your issue. Someone may have already asked this question/request.
-Please fill in as many of the fields as possible to facilitate the resolution or clarification of your question ❤️.
-
--->
+Please search open/closed issues before submitting. Someone might have asked the same thing before 😉!
 
 #### 1. Description:
 
-> Describe your request in one or two sentences:
+Please describe your request in one or two sentences:
+
+> ...
 
 ---
 
-#### 2. Problem/Justification of Request:
+#### 2. Problem Statement/Justification:
+
+Please provide valid reason(s) why this should be added.
+If this feature is related to a problem you've noticed, mention it as well.
 
-> Please describe the reason for this request to be added or changed. If it's related to a problem, please describe it as well.
+> ...
 
 ---
 
-#### 3. Proposed Solution:
+#### 3. Proposed Solution or AP:
 
-> Describe your idea for a solution to the problem.
+Please provide valid reason(s) why this should be added.
+If this feature is related to a problem you've noticed, mention it as well.
+
+> ...
 
 ---
 
 #### 4. Alternatives:
 
-> What other alternatives were considered before ordering this feature?
+What alternative solutions have you considered before making this request?
+
+> ...
 
 ---
 
 #### 5. Additional Information:
 
-> Information, details or resources (links, screenshots, etc.) that will facilitate this task.
+What resources (links, screenshots, etc.) do you have to assist this effort?
+
+> ...

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,51 @@
+name: "Feature Request"
+description: "Request a feature or enhancement"
+labels: ["needs triage"]
+body:
+  - type: "markdown"
+    attributes:
+      value: |
+        Thanks for filing an issue 😄!
+
+        Please search open/closed issues before submitting. Someone
+        might have asked the same thing before 😉!
+  - type: "textarea"
+    id: "description"
+    attributes:
+      label: "Description"
+      description: "Please describe your request in one or two sentences."
+    validations:
+      required: true
+  - type: "textarea"
+    id: "justification"
+    attributes:
+      label: "Problem Statement/Justification"
+      description: |
+        Please provide valid reason(s) why this should be added 
+        If this feature is related to a problem you've noticed, mention it as
+        well.
+    validations:
+      required: true
+  - type: "textarea"
+    id: "proposed-solution"
+    attributes:
+      label: "Proposed Solution or API"
+      description: |
+        Please provide code snippets, gists, or links to the ideal
+        design or API.
+    validations:
+      required: true
+  - type: "textarea"
+    id: "alternatives"
+    attributes:
+      label: "Alternatives"
+      description: |
+        What alternative solutions have you considered before making this
+        request?
+  - type: "textarea"
+    id: "additional-information"
+    attributes:
+      label: "Additional Information"
+      description: |
+        What resources (links, screenshots, etc.) do you have to assist this
+        effort?