chore: import upstream snapshot with attribution

This commit is contained in:
wehub-resource-sync
2026-07-13 12:24:59 +08:00
commit 3fc658859c
6 changed files with 141 additions and 0 deletions
+58
View File
@@ -0,0 +1,58 @@
name: Bug report
description: Create a report to help us improve
labels: ["t/bug"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to fill out this bug report!
**Please update OrbStack** to the latest version before reporting a bug. Your issue may already be fixed.
- type: textarea
id: describe
attributes:
label: Describe the bug
description: What went wrong?
placeholder: A clear and concise description of what the bug is.
validations:
required: true
- type: textarea
id: reproduce
attributes:
label: To Reproduce
description: Steps to reproduce the behavior.
placeholder: |
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
validations:
required: false
- type: textarea
id: expected
attributes:
label: Expected behavior
description: What should have happened?
placeholder: |
A clear and concise description of what you expected to happen.
validations:
required: false
- type: textarea
id: diag
attributes:
label: Diagnostic report (REQUIRED)
description: |
Click "Upload Diagnostics" in OrbStack's Help menu (or run the "orb report" command), then paste the output here.
This is private and only OrbStack developers can see the report.
placeholder: |
REQUIRED. Paste here.
validations:
required: false
- type: textarea
id: additional
attributes:
label: Screenshots and additional context (optional)
description: Add any other context about the problem here, such as screenshots.
validations:
required: false
+20
View File
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: t/feature
assignees: ''
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.