Adds a config.yml chooser and two markdown templates: - bug_report.md — structured bug report with reproduction steps, environment info, and screenshot slot - feature_request.md — enhancement/UX/refactor request with problem statement, proposed solution, and alternatives Both follow the project's bracket-prefix title convention.
43 lines
917 B
Markdown
43 lines
917 B
Markdown
---
|
|
name: 🐛 Bug report
|
|
description: Report a bug or unexpected behaviour
|
|
title: '[bug] '
|
|
labels: bug
|
|
assignees: ''
|
|
---
|
|
|
|
## Describe the bug
|
|
|
|
<!-- A clear and concise description of what the bug is. -->
|
|
|
|
## To reproduce
|
|
|
|
Steps to reproduce the behaviour:
|
|
|
|
1. Go to '…'
|
|
2. Tap on '…'
|
|
3. Scroll to '…'
|
|
4. See error
|
|
|
|
## Expected behaviour
|
|
|
|
<!-- What should have happened instead? -->
|
|
|
|
## Screenshots / screen recordings
|
|
|
|
<!-- If applicable, add screenshots or a screen recording to help explain the problem. -->
|
|
|
|
## Environment
|
|
|
|
- Device: <!-- e.g. Pixel 8, Samsung Galaxy S24 -->
|
|
- Android version: <!-- e.g. Android 14, Android 15 -->
|
|
- App version: <!-- e.g. v1.2.3, or the commit SHA -->
|
|
- Hermes dashboard version: <!-- if known -->
|
|
|
|
## Additional context
|
|
|
|
<!--
|
|
Anything else? Error logs, crash reports (adb logcat), network trace, etc.
|
|
Remove any sensitive info (tokens, hostnames) before pasting.
|
|
-->
|