Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
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
11 changes: 0 additions & 11 deletions .github/ISSUE_TEMPLATE/bug_report.md

This file was deleted.

45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: Bug Report
description: Did something not work as expected?
title: "[Bug]: "
labels: ["bug"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of setting the labels, are we able to use the new issue types here?

There's one each for "Feature" and "Bug", and if we stop introducing more issues tagged with "bug", we might be able to use labels more for categorising the types of issues.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw that type is mentioned in the documentation, but when I tried to set it, I got a syntax error and couldn’t configure it.

Is this something that’s only available for Organizations, by any chance?

If possible, could you configure it on your side?

body:
- type: markdown
attributes:
value: |
Did something not work as expected?

- type: textarea
id: what-happened
attributes:
label: What were you trying to do?
description: Also tell us, what did you expect to happen?
validations:
required: true

- type: textarea
id: logs
attributes:
label: What did you end up with?
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
placeholder: logs, or, even better, example apps are great!
render: shell
validations:
required: false

- type: input
id: rails-versions
attributes:
label: What Rails versions are you running?
description: How can we get in touch with you if we need more info?
placeholder: ex) 7.0, 7.1
validations:
required: false

- type: input
id: administrate-versions
attributes:
label: What Administrate versions are you running?
description: How can we get in touch with you if we need more info?
placeholder: ex) 1.0.0, 0.20.1
validations:
required: false
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: true
9 changes: 0 additions & 9 deletions .github/ISSUE_TEMPLATE/feature_request.md

This file was deleted.

32 changes: 32 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
name: Feature Request
description: Is there something new you'd like to see in administrate?
title: "[Feat]: "
labels: ["feature-request"]
body:
- type: markdown
attributes:
value: |
Is there something new you'd like to see in administrate?

- type: textarea
id: what-would-you-want
attributes:
label: What would you like to be able to do?
description: Also tell us, can you provide some examples?
validations:
required: true

- type: textarea
id: how-could-we-go
attributes:
label: How could we go about implementing that?
validations:
required: false

- type: checkboxes
id: other-approaches
attributes:
label: Can you think of other approaches to the problem?
options:
- label: Yes, I can.
required: true