Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update issue templates #1184

Merged
merged 3 commits into from
Sep 27, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 0 additions & 35 deletions .github/ISSUE_TEMPLATE/bug_report.md

This file was deleted.

42 changes: 42 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
name: "\U0001F41E Bug report"
description: Report an issue with Hilla
labels: ["bug"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to fill out this bug report!
- type: textarea
id: bug-description
attributes:
label: Describe the bug
description: A clear and concise description of what the bug is. If you intend to submit a PR for this issue later, please let us know here.
placeholder: Bug description
validations:
required: true
- type: textarea
id: expected-behavior
attributes:
label: Expected-behavior
description: Describe what the expected behavior you think, and we will validate on our designs.
placeholder: expected behavior
- type: textarea
id: reproduction
attributes:
label: Reproduction
description: Please tell us how to reproduce this issue step by step. If you have an example project to show, please provide us the link.
placeholder: Reproduction
validations:
required: true
- type: textarea
id: system-info
attributes:
label: System Info
description: Please let us know your environment when reproducing the issue.
placeholder: Operating System, Hilla version, Browsers type and version
validations:
required: true
- type: markdown
attributes:
value: |
If you think this ticket is important, add a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to help the community and maintainers prioritize this issue.
tarekoraby marked this conversation as resolved.
Show resolved Hide resolved
20 changes: 0 additions & 20 deletions .github/ISSUE_TEMPLATE/feature_request.md

This file was deleted.

38 changes: 38 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
name: "\U0001F680 Feature Request"
description: Asking for a new feature/API in Hilla
labels: ["feature request"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to fill out this feature request!
- type: textarea
id: feature-description
attributes:
label: Describe your motivation
description: A concise description of why you are proposing a change. For example, you would like a new feature to solve a use-case, or you want an existing feature changed because it is difficult to use.
placeholder: describe the current issue with existing feature/API
validations:
required: true
- type: textarea
id: expected-solution
attributes:
label: Describe the solution you'd like
description: Provide a clear and concise description of what you want to happen.
placeholder: expected solution
- type: textarea
id: alternatives
attributes:
label: Describe alternatives you've considered
description: Provide information about other solutions you've tried or researched.
placeholder: alternatives
- type: textarea
id: additional
attributes:
label: Additional context
description: Is there anything else you can add about the proposal?
placeholder: additional context
- type: markdown
attributes:
value: |
If you think this ticket is important, add a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to help the community and maintainers prioritize this issue.
tarekoraby marked this conversation as resolved.
Show resolved Hide resolved