diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml index 64c0194688..34663b5eda 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yaml +++ b/.github/ISSUE_TEMPLATE/bug_report.yaml @@ -8,11 +8,11 @@ body: value: | # Bug Report - Use this for real, reproducible bugs. Include the affected workflow, the expected result, the actual result, and the details needed for someone else to reproduce it. + Use this for real, reproducible bugs. A clear issue is the most useful contribution: include the affected workflow, the expected result, the actual result, and the details needed for someone else to reproduce it. Before submitting, search open and closed [Issues](https://github.com/open-webui/open-webui/issues) and [Discussions](https://github.com/open-webui/open-webui/discussions). The issue may already be reported or fixed on `dev`. - Please do not open a code pull request for this report unless a maintainer asks for one. Actionable reproduction details are the most useful next step. + Please do not open a code pull request for this report unless a maintainer asks for one, or the change is only i18n/localization. If you want to share code as reference, include it here as a local diff or patch. Actionable reproduction details are the most useful next step. Security vulnerabilities must not be reported publicly. Use the [GitHub security page](https://github.com/open-webui/open-webui/security) instead. @@ -25,6 +25,8 @@ body: required: true - label: I checked whether this is already fixed on the `dev` branch or latest source. required: true + - label: I understand that maintainers want a well-written issue before any code pull request. + required: true - label: I am using the latest available version of Open WebUI for my install method. required: true - label: This is not a security vulnerability. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml index 52c10fc31d..87a915960c 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yaml +++ b/.github/ISSUE_TEMPLATE/feature_request.yaml @@ -8,11 +8,11 @@ body: value: | # Feature Request - Describe the requested behavior, the problem it solves, and any examples, mockups, screenshots, or workflows that clarify the request. + Describe the requested behavior, the problem it solves, and any examples, mockups, screenshots, or workflows that clarify the request. A clear issue or discussion is the most useful contribution. Search open and closed [Issues](https://github.com/open-webui/open-webui/issues) and [Discussions](https://github.com/open-webui/open-webui/discussions) before submitting. If the request needs broad product, UX, architecture, compatibility, or maintenance discussion, please start in [Discussions](https://github.com/open-webui/open-webui/discussions) so the community can weigh in. - Please do not open a code pull request for this request unless a maintainer asks for one. Clear product context is the most useful next step. + Please do not open a code pull request for this request unless a maintainer asks for one, or the change is only i18n/localization. If you want to share code as reference, include it here as a local diff or patch. Clear product context is the most useful next step. Security vulnerabilities must not be reported publicly. Use the [GitHub security page](https://github.com/open-webui/open-webui/security) instead. @@ -25,6 +25,8 @@ body: required: true - label: I checked whether this already exists on the `dev` branch or latest source. required: true + - label: I understand that maintainers want a well-written issue or discussion before any code pull request. + required: true - label: This request is not a security vulnerability. required: true diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 5aa1fd3b35..a568080607 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,25 +1,27 @@ # Pull Request -Thanks for helping improve Open WebUI. Please make sure the linked Issue or Discussion explains the user-facing problem, the expected outcome, and any relevant examples or constraints. +Thanks for wanting to improve Open WebUI. The most useful contribution is usually a clear, well-written Issue, not an unsolicited code pull request. -Code contributions are not the default path. Open a code pull request only when a maintainer asks for one, or for narrow i18n/localization updates. For real, reproducible bugs, start with a well-described [Issue](https://github.com/open-webui/open-webui/issues). For feature requests, UI/UX changes, behavior changes, architecture changes, suspected fixes, or unconfirmed approaches, start with an active [Discussion](https://github.com/open-webui/open-webui/discussions). +Open a code pull request only when a maintainer asks for one, or when the change is only i18n/localization. For real, reproducible bugs, start with a well-described [Issue](https://github.com/open-webui/open-webui/issues). For feature requests, UI/UX changes, behavior changes, architecture changes, suspected fixes, or unconfirmed approaches, start with an active [Discussion](https://github.com/open-webui/open-webui/discussions). -If you have implementation notes, include them as reference in the Issue or Discussion. A local diff, patch, or branch can be useful context, but it does not mean a pull request is expected or will be reviewed. +Before continuing, make sure the linked Issue or Discussion explains the user-facing problem, the expected outcome, the affected workflow, and any examples, logs, screenshots, constraints, or reproduction details needed for maintainers to evaluate it. + +If you have implementation notes, include them as reference in the Issue or Discussion. If you want to share code as reference, include it there as a local diff, patch, or branch note. Do not open a pull request for reference code. Unsolicited PRs may be closed without review, especially when they introduce product, architecture, compatibility, dependency, or maintenance decisions that have not been discussed. ## Checklist - [ ] This PR targets the `dev` branch. -- [ ] This PR links to a confirmed Issue or active Discussion: `Closes #___` / `Relates to #___`. +- [ ] This PR links to a well-described, confirmed Issue or active Discussion: `Closes #___` / `Relates to #___`. - [ ] A maintainer explicitly asked me to open this PR, or this PR only updates i18n/localization. - [ ] The change is one logical unit with no unrelated commits. - [ ] I matched nearby code patterns and avoided unnecessary new settings, abstractions, or dependencies.