感谢你帮助改善 Reqix。本仓库是社区与支持中心，不是 Reqix 源代码仓库。
- 在 Discussions 回答使用问题或分享已验证的工作流；
- 在 Ideas 描述真实场景、当前阻碍和期望结果；
- 使用 Issue 表单报告可复现的产品缺陷或文档问题；
- 帮助识别重复问题、补充公开文档链接，或提醒发布者删除敏感数据。
Reqix 产品代码不在本仓库中，也不接受产品代码 Pull Request。通常无需为问题模板或社区政策直接提交 Pull Request；请先在 General Discussions 说明你发现的问题和建议修改，维护者会评估并更新。
未经维护者事先确认的 Pull Request 可能会被关闭。提交内容不得包含反编译的 Reqix 实现、绕过许可或安全限制的方法、第三方专有代码，或任何敏感数据。
- 使用的 Reqix、Chrome 或 Edge 版本；
- 清晰的当前行为与期望行为；
- 不包含敏感信息的最小复现步骤；
- 已经搜索过的 Issue、Discussion 或文档；
- 完整脱敏的截图或日志（仅在确有必要时）。
所有参与者都必须遵守 社区行为准则。安全漏洞必须按 安全政策 私密报告。
Thank you for helping improve Reqix. This repository is a community and support hub, not the Reqix source-code repository.
- Answer usage questions or share verified workflows in Discussions.
- Describe real workflows, current obstacles, and desired outcomes in Ideas.
- Use the Issue forms for reproducible product defects or documentation problems.
- Help identify duplicates, link to public documentation, or remind authors to remove sensitive data.
Reqix product code is not hosted here, and this repository does not accept product-code Pull Requests. You normally do not need to submit a Pull Request for forms or community policy changes; describe the problem and proposed outcome in General Discussions first so maintainers can evaluate and update it.
Pull Requests submitted without prior maintainer confirmation may be closed. Submissions must never include reverse-engineered Reqix internals, methods for bypassing licensing or security controls, third-party proprietary code, or sensitive data.
- Reqix and Chrome or Edge versions.
- Clear current and expected behavior.
- Minimal reproduction steps with no sensitive information.
- Relevant Issues, Discussions, or documentation already searched.
- Fully sanitized screenshots or logs only when necessary.
All participants must follow the Community Code of Conduct. Report security vulnerabilities privately according to the Security Policy.