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

Issue Templates #930

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

aniculescu
Copy link

From issue #865, this PR introduces two templates:

  • Bugs
  • Default

Sample screenshot:
image

Additionally, a small update to docs (contributing.md) to reflect these changes.

Copy link
Collaborator

@dherman dherman left a comment

Choose a reason for hiding this comment

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

Thank you for this contribution! I did not know how the issue template configuration format worked, so I appreciate you diving in and figuring it out. I've made a few suggestions to try to optimize the balance of the informative/expensive ROI ratio, but I really like the general direction.

.github/ISSUE_TEMPLATE/bug_report.yml Show resolved Hide resolved
**Note**: We encourage you to [submit an RFC](https://github.com/neon-bindings/rfcs) if you would like to propose a **design change** or a **new feature** for the Neon API or the Neon command-line tool.
______

In addition to the `bug` label, consider adding others you might find relevant:
Copy link
Collaborator

Choose a reason for hiding this comment

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

This table is nice documentation for us to have somewhere, but I don't think it belongs in our issue template. I don't think we have a way to enable non-maintainers to attach labels, and I think the ROI isn't there anyway (the benefit of getting help with triage doesn't pay for the friction it adds to casually filing issues).

Copy link
Author

Choose a reason for hiding this comment

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

Good feedback, thanks. I was struggling to maintain that same ratio, ultimately I figured it's easier to cut things out than not have enough detail. Maybe the labels table is best moved to the contributing doc?

Thanks in advance for taking the time to file this issue!
We hope this simple template will improve issue resolution time and minimize the need for _context discovery_ discussions.
______
**Note**: We encourage you to [submit an RFC](https://github.com/neon-bindings/rfcs) if you would like to propose a **design change** or a **new feature** for the Neon API or the Neon command-line tool.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why don't we add just one more category for Feature Requests and add this note to that one instead. For bug reports I don't think they'll generally need an RFC.

Copy link
Author

Choose a reason for hiding this comment

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

👍 - Probably not worded great, but the intent was to say: don't use a bug template to describe a more fundamental change. I"ll add the feature_request type.

@@ -0,0 +1,61 @@
name: New Issue
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why don't we call this "All Other Issues" or something like that, to make it really clear that it's the catch-all case.

- type: markdown
attributes:
value: |
Thanks in advance for taking the time to file this issue!
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's make the structure for this kind of issue report extremely minimal, so that we minimize the risk of people giving up on filing issues.

Copy link
Member

Choose a reason for hiding this comment

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

I think this is a good idea. Make the "other" issue nothing but an open text field.

- type: input
id: npm_version
attributes:
label: "Node Package Manager version: "
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think "Node" here is unnecessary, just "Package Manager version" is good.

Copy link
Member

Choose a reason for hiding this comment

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

Perhaps just "Package Manager" to make space for alternate package managers (yarn, pnpm).

    attributes:
      label: "Package Manage: "
      description: "Please specify the package manager and version you are running (`npm -v`)"
      placeholder: "npm 8.19.2"

Copy link
Author

Choose a reason for hiding this comment

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

    attributes:
      label: "Package Manager & version: "
      description: "Please specify the package manager your are using and its version"
      placeholder: "example: npm 8.19.2"

How's this?

CONTRIBUTING.md Outdated
@@ -6,10 +6,11 @@ Neon welcomes contribution from everyone. Here are some resources to help you jo

### Issue reports

We welcome issues and aim to keep the barrier low. Just [file a GitHub issue](https://github.com/neon-bindings/neon/issues)
like normal---we don't require issue templates or have any particular process.
We welcome issues and aim to keep the barrier low. For clarity and efficiency, we created two simple issue templates:
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we add a third, then s/two/three/

CONTRIBUTING.md Outdated
like normal---we don't require issue templates or have any particular process.
We welcome issues and aim to keep the barrier low. For clarity and efficiency, we created two simple issue templates:
- [Bug Report](https://github.com/neon-bindings/issues/new?assignees=&labels=bug&template=bug_report.yml&title=🐛+%5BBUG%5D+-+<title>)
- [General Neon Issue](https://github.com/neon-bindings/issues/new?assignees=&labels=&template=default_issue.yml&title=Neon+Issue)
Copy link
Collaborator

Choose a reason for hiding this comment

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

(If we add a third, add the text here)

CONTRIBUTING.md Outdated

That said, the more information you can provide to help us reproduce your issue, the better!
The more information you can provide, the better! Thanks in advance! ❤️
Copy link
Collaborator

Choose a reason for hiding this comment

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

How about "The more information you can provide, the better we can help you get your issue resolved!" so we explain it explicitly in terms of how we are here to help the contributor?

- type: input
id: neon_version
attributes:
label: "NEON version(s): "
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
label: "NEON version(s): "
label: "Neon version(s): "

- type: input
id: npm_version
attributes:
label: "Node Package Manager version: "
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps just "Package Manager" to make space for alternate package managers (yarn, pnpm).

    attributes:
      label: "Package Manage: "
      description: "Please specify the package manager and version you are running (`npm -v`)"
      placeholder: "npm 8.19.2"

- type: markdown
attributes:
value: |
Thanks in advance for taking the time to file this issue!
Copy link
Member

Choose a reason for hiding this comment

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

I think this is a good idea. Make the "other" issue nothing but an open text field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants