bughz
/
code-server
mirror of https://github.com/coder/code-server.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
code-server/.github/ISSUE_TEMPLATE/bug-report.yml

93 lines
3.1 KiB
YAML
Raw Normal View History

chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
name: Bug report
description: File a bug report
title: "[Bug]: "
labels: ["bug", "triage"]
body:
- type: checkboxes
attributes:
label: Is there an existing issue for this?
description: Please search to see if an issue already exists for the bug you encountered.
options:
- label: I have searched the existing issues
required: true
- type: textarea
attributes:
label: OS/Web Information
description: |
examples:
- **Web Browser**: Chrome
- **Local OS**: macOS
- **Remote OS**: Ubuntu
- **Remote Architecture**: amd64
- **`code-server --version`**: 4.0.1
value: |
- Web Browser:
- Local OS:
- Remote OS:
- Remote Architecture:
- `code-server --version`:
validations:
chore: update bug-report.yaml (#4780) * chore: update bug-report.yml Fix `OS/Web Information` section and don't render as Markdown * chore: add repro steps to bug template
2022-01-25 05:58:26 +08:00
required: true
- type: textarea
attributes:
label: Steps to Reproduce
description: |
1. open code-server
2. install extension
3. run command
value: |
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
2023-12-19 06:54:18 +08:00
1.
chore: update bug-report.yaml (#4780) * chore: update bug-report.yml Fix `OS/Web Information` section and don't render as Markdown * chore: add repro steps to bug template
2022-01-25 05:58:26 +08:00
2.
3.
validations:
required: true
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
- type: textarea
attributes:
label: Expected
description: What should happen?
validations:
required: true
- type: textarea
attributes:
label: Actual
description: What actually happens?
validations:
required: true
- type: textarea
id: logs
attributes:
label: Logs
revert(docs): partially revert 326a1d1862872955cec062030df2bd103799a1eb (#5095) We tried to switch from `yarn` to `npm` because `yarn` ignores lockfiles but learned that we missed a few key things. For now, we are reverting docs and a few other changes that suggested using `npm` instead of `yarn` until we fully remove `yarn` from the codebase. t Please enter the commit message for your changes. Lines starting
2022-04-14 01:15:21 +08:00
description: Run code-server with the --verbose flag and then paste any relevant logs from the server, from the browser console and/or the browser network tab. For issues with installation, include installation logs (i.e. output of `yarn global add code-server`).
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
- type: textarea
attributes:
label: Screenshot/Video
description: Please include a screenshot, gif or screen recording of your issue.
validations:
required: false
- type: checkboxes
attributes:
chore: update bug report template (#5261) * chore: update bug report template Add an additional checkbox to the bug report template * Update .github/ISSUE_TEMPLATE/bug-report.yml
2022-06-14 03:51:30 +08:00
label: Does this issue happen in VS Code or GitHub Codespaces?
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
2023-12-19 06:54:18 +08:00
description: Please try reproducing this issue in VS Code and GitHub Codespaces. If the bug reproduces in either VS Code or GitHub Codespaces, please submit the issue upstream instead (https://github.com/microsoft/vscode).
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
options:
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
2023-12-19 06:54:18 +08:00
- label: I tested this in native VS Code.
required: false
- label: This does not happen in native VS Code.
required: false
- label: I tested this in GitHub Codespaces.
required: false
- label: This does not happen in GitHub Codespaces.
required: false
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
- type: checkboxes
attributes:
Use secure context in bug report template Some folks run over localhost, which will work just fine for service workers.
2023-10-12 09:18:16 +08:00
label: Are you accessing code-server over a secure context?
description: code-server relies on service workers (which only work in secure contexts) for many features. Double-check that you are using a secure context like HTTPS or localhost.
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
options:
Use secure context in bug report template Some folks run over localhost, which will work just fine for service workers.
2023-10-12 09:18:16 +08:00
- label: I am using a secure context.
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
2023-12-19 06:54:18 +08:00
required: false
chore: update issue templates (#4768) * chore: delete release issue template * chore: use bug-report form template * chore: clean up config.yml for templates * chore: clean up doc issue template * chore: clean up feature request template
2022-01-21 00:39:31 +08:00
- type: textarea
attributes:
label: Notes
description: Please include any addition notes that will help us resolve this issue.
validations:
required: false