Skip to content

chore: add bug issue template #150

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

Merged
merged 9 commits into from
Apr 29, 2025
Merged

chore: add bug issue template #150

merged 9 commits into from
Apr 29, 2025

Conversation

fmenezes
Copy link
Collaborator

No description provided.

@Copilot Copilot AI review requested due to automatic review settings April 28, 2025 17:03
@fmenezes fmenezes requested a review from a team as a code owner April 28, 2025 17:03
@fmenezes fmenezes enabled auto-merge (squash) April 28, 2025 17:03
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a bug report template to GitHub's issue templates to help users report bugs more effectively.

  • Introduces a structured Markdown bug report template with sections such as Description, Affected Apps, Affected Models, and Additional Context.
  • Sets default labels and metadata for new bug reports.

@fmenezes fmenezes changed the title Add bug issue template chore: add bug issue template Apr 28, 2025
- label: Windsurf
- label: VSCode
- label: VSCode Insiders
- label: Claude Desktop
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we have Other here?

- label: "Claude 3.5 Sonnet"
- label: "Claude 3.7 Sonnet"
- label: "GPT-4a"
- label: "o4-mini"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Similarly, perhaps add "Other" or just leave it as an input so that we don't have to constantly update the list.

label: "Screenshots"
description: "If applicable, add links to screenshots to help explain your problem."
placeholder: "e.g., Screenshot URLs or descriptions."
- type: textarea
Copy link
Collaborator

Choose a reason for hiding this comment

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

We probably don't need this since most of it will already have been included in the description.

label: "Expected Behavior"
description: "Describe what you expected to happen."
placeholder: "e.g., The app should not crash and should display the dashboard."
- type: textarea
Copy link
Collaborator

Choose a reason for hiding this comment

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

Probably don't need this either - I expect people will add all the context they can think of in the description already.

- type: textarea
id: screenshots
attributes:
label: "Screenshots"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I feel screenshots might not be relevant here as we're building a text interface, so I hope people will copy-paste issues they encounter rather than sending us a screenshot of a conversation with a chatbot. Additionally, pasting links to screenshots is a bit annoying and a potential malware vector (I am always extremely cautious when clicking any user-supplied links). Instead, we could add a readonly (i.e. markdown) section, instructing users that if they need to provide additional context or screenshots, they can add them as a comment after filing the issue (since adding a comment allows you to directly upload the image).

@fmenezes fmenezes requested a review from nirinchev April 29, 2025 08:51
Copy link
Collaborator

@gagik gagik left a comment

Choose a reason for hiding this comment

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

Nice

@fmenezes fmenezes merged commit 264aba1 into main Apr 29, 2025
15 checks passed
@fmenezes fmenezes deleted the fmenezes/issue_templates branch April 29, 2025 10:07
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.

3 participants