github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[PR #11232] [CLOSED] Feature/tmi/432 webui integration #9488

New Issue
Closed
opened 2025-11-11 18:23:56 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 18:23:56 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/11232
Author: @itomek
Created: 3/5/2025
Status: ❌ Closed

Base: main ← Head: feature/tmi/432-webui-integration

📝 Commits (5)

  • 216164b docs: Add arch and install diagrams
  • 753ff86 chore: Add GitHub Actions workflow for releasing artifacts and update configurations
  • da5866c chore: Update build-release workflow with GitHub Actions permissions
  • 83187f3 chore: Update build-release workflow branch to feature branch
  • 4c7d8da chore: Update build-release workflow name for GAIA release

📊 Changes

9 files changed (+178 additions, -96 deletions)

View changed files

➕ .actrc (+2 -0)
📝 .github/workflows/build-release.yml (+7 -13)
➕ .github/workflows/release-artifact.yaml (+31 -0)
📝 .gitignore (+1 -0)
➕ .vscode/launch.json (+13 -0)
➕ .vscode/tasks.json (+8 -0)
📝 README.md (+5 -83)
➕ docs/architecture.md (+80 -0)
➕ docs/install.md (+31 -0)

📄 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/11232 **Author:** [@itomek](https://github.com/itomek) **Created:** 3/5/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feature/tmi/432-webui-integration` --- ### 📝 Commits (5) - [`216164b`](https://github.com/open-webui/open-webui/commit/216164b888936375df6447325917366ff2babc48) docs: Add arch and install diagrams - [`753ff86`](https://github.com/open-webui/open-webui/commit/753ff86e1972ddda031493b415f1a608519176f3) chore: Add GitHub Actions workflow for releasing artifacts and update configurations - [`da5866c`](https://github.com/open-webui/open-webui/commit/da5866c35bbc347d4092feabd48201f7cf7e451b) chore: Update build-release workflow with GitHub Actions permissions - [`83187f3`](https://github.com/open-webui/open-webui/commit/83187f379e703c585a60fcab73cd1981a6062e80) chore: Update build-release workflow branch to feature branch - [`4c7d8da`](https://github.com/open-webui/open-webui/commit/4c7d8da78e20cb11cdab0bf73c6416fb0d60767b) chore: Update build-release workflow name for GAIA release ### 📊 Changes **9 files changed** (+178 additions, -96 deletions) <details> <summary>View changed files</summary> ➕ `.actrc` (+2 -0) 📝 `.github/workflows/build-release.yml` (+7 -13) ➕ `.github/workflows/release-artifact.yaml` (+31 -0) 📝 `.gitignore` (+1 -0) ➕ `.vscode/launch.json` (+13 -0) ➕ `.vscode/tasks.json` (+8 -0) 📝 `README.md` (+5 -83) ➕ `docs/architecture.md` (+80 -0) ➕ `docs/install.md` (+31 -0) </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 2025-11-11 18:23:56 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#9488
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?