mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-08-04 06:12:10 +03:00

Files

diegosouzapw 52221488d0 docs: sync all 30 language READMEs with v1.7.3 features + create workflow files

- Synced feature tables across all 28 translated READMEs (Model Aliases, Background Degradation, Rate Limit Persistence, Token Refresh Resilience)
- Updated 6 docs/i18n/*/FEATURES.md with new Settings description
- Created workflows: update-docs.md (with multi-language sync step), generate-release.md, issue-triage.md

2026-03-01 22:02:38 -03:00

1.2 KiB

Raw Blame History

description

description
How to respond to GitHub issues with insufficient information

Issue Triage Workflow

Respond to GitHub issues that need more information before they can be investigated.

Steps

1. Identify issues needing triage

gh issue list --state open --limit 20

2. Evaluate each issue

Check if the issue has:

Clear reproduction steps
Environment details (OS, Node.js version, OmniRoute version)
Error logs/screenshots
Expected vs actual behavior

3. Respond with triage template

For issues missing information:

Thank you for reporting this issue! To help us investigate, please provide:

1. **OmniRoute version**: (`omniroute --version`)
2. **Node.js version**: (`node --version`)
3. **Operating system**: (e.g., Ubuntu 24.04, macOS 15, Windows 11)
4. **Installation method**: (npm, Docker, source)
5. **Steps to reproduce**: (exact commands/actions that trigger the issue)
6. **Error logs**: (paste relevant logs from the console)
7. **Expected behavior**: (what should happen)

This will help us debug and resolve your issue faster. 🙏

4. Label the issue

Add appropriate labels: needs-info, bug, enhancement, question, etc.

gh issue edit <NUMBER> --add-label "needs-info"

1.2 KiB Raw Blame History