From b838860dc06a45f8ffa9b8bdd036c60338670f1f Mon Sep 17 00:00:00 2001 From: Timothy Jaeryang Baek Date: Tue, 18 Aug 2026 19:30:42 -0700 Subject: [PATCH] refac --- .github/pull_request_template.md | 22 +++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index b180ed8795..6077b077f6 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -2,18 +2,26 @@ ⚠️ CRITICAL CHECKS FOR CONTRIBUTORS (READ, DON'T DELETE) ⚠️ 1. Target the `dev` branch. PRs targeting `main` will be automatically closed. 2. First-time contributors should not open pull requests directly unless the pull request contains only i18n/localization updates. - Please start with a clear, detailed Issue or Discussion so maintainers can review the problem, scope, and proposed approach before any implementation is submitted. - If you already have code, share the proposed diff in the Issue or Discussion for review. - Open a pull request only after a maintainer explicitly asks you to do so. - First-time pull requests opened without maintainer invitation will be redirected to the Issue or Discussion process. + Do not open a PR as the first step. + For real, reproducible bugs, start with a well-described Issue that explains the problem, why it matters, and what outcome you are looking for. + For feature requests, enhancements, behavior changes, UI/UX changes, architecture changes, suspected fixes, or unconfirmed approaches, start with an active Discussion. + If you want to propose an implementation, include a local diff or patch in the Issue or Discussion. + We may close unsolicited PRs without review. + Contributors with a history of successful merged PRs may be given more latitude. 3. Do NOT delete the CLA section at the bottom. It is required for the bot to accept your PR. --> # Pull Request Checklist -### Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to **discuss your idea with the community first** before creating a pull request, and describe your changes before submitting a pull request. Merely opening a discussion is not enough, it needs to be actively discussed. +### Do not open a pull request as the first step. -This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. +For real, reproducible bugs, start with a well-described [Issue](https://github.com/open-webui/open-webui/issues) that explains the problem, why it matters, and what outcome you are looking for. + +For feature requests, enhancements, behavior changes, UI/UX changes, architecture changes, suspected fixes, or unconfirmed approaches, start with an active [Discussion](https://github.com/open-webui/open-webui/discussions). Merely opening a discussion is not enough; it needs to be actively discussed. + +If you want to propose an implementation, include a local diff or patch in the Issue or Discussion for context. + +Unsolicited PRs may be closed without review. Contributors with a history of successful merged PRs may be given more latitude.