[PR #7478] [CLOSED] Feature/test workflow #37696

Closed
opened 2026-04-25 11:03:02 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/7478
Author: @SSolicki
Created: 11/29/2024
Status: Closed

Base: mainHead: feature/test-workflow


📝 Commits (7)

  • 993fecb igang igjen
  • 36947d3 miljø spec
  • bcfcf97 blæ
  • 1eea7cd jepp
  • f699589 chore: add deployment documentation and automation workflow
  • f629ade docs: update deployment documentation and close debug notes
  • 25cb6bd docs: update deployment test checklist with PR steps

📊 Changes

32 files changed (+1807 additions, -112 deletions)

View changed files

.github/workflows/dev-to-test-merge.yml (+46 -0)
📝 Dockerfile (+35 -0)
📝 README.md (+29 -50)
backend/Dockerfile (+32 -0)
debug.md (+33 -0)
deployment.md (+123 -0)
deploymenttest.md (+154 -0)
docker-compose.a1111-test.yaml (+0 -31)
docker-compose.amdgpu.yaml (+0 -8)
docker-compose.api.yaml (+0 -5)
docker-compose.data.yaml (+0 -4)
docker-compose.dev.yaml (+70 -0)
docker-compose.gpu.yaml (+0 -11)
docker-compose.prod.yaml (+74 -0)
📝 docker-compose.template.yaml (+0 -0)
docker-compose.test.yaml (+91 -0)
docs/STRATEGY.md (+142 -0)
docs/closedbug.md (+50 -0)
docs/debug.md (+76 -0)
docs/futurework.md (+61 -0)

...and 12 more files

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests for validating the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

  • [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

  • [List any new features, functionalities, or additions]

Changed

  • [List any changes, updates, refactorings, or optimizations]

Deprecated

  • [List any deprecated functionality or features that have been removed]

Removed

  • [List any removed features, files, or functionalities]

Fixed

  • [List any fixes, corrections, or bug fixes]

Security

  • [List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

  • BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

  • [Insert any additional context, notes, or explanations for the changes]
    • [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

  • [Attach any relevant screenshots or videos demonstrating the changes]

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/7478 **Author:** [@SSolicki](https://github.com/SSolicki) **Created:** 11/29/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feature/test-workflow` --- ### 📝 Commits (7) - [`993fecb`](https://github.com/open-webui/open-webui/commit/993fecbe62edac40d7df816415139f8b3870e7c3) igang igjen - [`36947d3`](https://github.com/open-webui/open-webui/commit/36947d3902833b78961ba7e925650bb2c480e841) miljø spec - [`bcfcf97`](https://github.com/open-webui/open-webui/commit/bcfcf978de849e2aa0a5c8faf503821c9ab13790) blæ - [`1eea7cd`](https://github.com/open-webui/open-webui/commit/1eea7cd8a3693922b1d172850c7625d69c97e995) jepp - [`f699589`](https://github.com/open-webui/open-webui/commit/f6995890bac043e0966a64890a39e60c0d74ab17) chore: add deployment documentation and automation workflow - [`f629ade`](https://github.com/open-webui/open-webui/commit/f629ade258feda0b9b0412240ac0ba16ec7c5935) docs: update deployment documentation and close debug notes - [`25cb6bd`](https://github.com/open-webui/open-webui/commit/25cb6bdca62d550cc57e27de0e50f1b0b38510d9) docs: update deployment test checklist with PR steps ### 📊 Changes **32 files changed** (+1807 additions, -112 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/dev-to-test-merge.yml` (+46 -0) 📝 `Dockerfile` (+35 -0) 📝 `README.md` (+29 -50) ➕ `backend/Dockerfile` (+32 -0) ➕ `debug.md` (+33 -0) ➕ `deployment.md` (+123 -0) ➕ `deploymenttest.md` (+154 -0) ➖ `docker-compose.a1111-test.yaml` (+0 -31) ➖ `docker-compose.amdgpu.yaml` (+0 -8) ➖ `docker-compose.api.yaml` (+0 -5) ➖ `docker-compose.data.yaml` (+0 -4) ➕ `docker-compose.dev.yaml` (+70 -0) ➖ `docker-compose.gpu.yaml` (+0 -11) ➕ `docker-compose.prod.yaml` (+74 -0) 📝 `docker-compose.template.yaml` (+0 -0) ➕ `docker-compose.test.yaml` (+91 -0) ➕ `docs/STRATEGY.md` (+142 -0) ➕ `docs/closedbug.md` (+50 -0) ➕ `docs/debug.md` (+76 -0) ➕ `docs/futurework.md` (+61 -0) _...and 12 more files_ </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests for validating the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Prefix:** To cleary categorize this pull request, prefix the pull request title, using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 11:03:02 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#37696