[PR #8745] [CLOSED] Workflow #22282

New Issue

GiteaMirror · 2026-04-20T04:02:50-05:00

GiteaMirror commented

2026-04-20 04:02:50 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/8745
Author: @leoguillaume
Created: 1/22/2025
Status: ❌ Closed

Base: main ← Head: workflow

📝 Commits (7)

95466fe feat: add albert-api to env example
aac3f55 update docker compose to add albert api
1abc291 chore: add dsfr
ca72e03 init commit workflow
369bc2c add workflow
5a79379 build and deploy on workflow branch
c602d7b update build & deploy

📊 Changes

15 files changed (+83 additions, -1066 deletions)

View changed files

📝 .env.example (+3 -0)
➖ .github/workflows/build-release.yml (+0 -72)
➕ .github/workflows/build_and_deploy.yml (+65 -0)
➖ .github/workflows/codespell.disabled (+0 -25)
➖ .github/workflows/deploy-to-hf-spaces.yml (+0 -63)
➖ .github/workflows/docker-build.yaml (+0 -477)
➖ .github/workflows/format-backend.yaml (+0 -39)
➖ .github/workflows/format-build-frontend.yaml (+0 -57)
➖ .github/workflows/integration-test.yml (+0 -253)
➖ .github/workflows/lint-backend.disabled (+0 -27)
➖ .github/workflows/lint-frontend.disabled (+0 -21)
➖ .github/workflows/release-pypi.yml (+0 -32)
📝 docker-compose.yaml (+4 -0)
📝 package-lock.json (+10 -0)
📝 package.json (+1 -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/8745 **Author:** [@leoguillaume](https://github.com/leoguillaume) **Created:** 1/22/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `workflow` --- ### 📝 Commits (7) - [`95466fe`](https://github.com/open-webui/open-webui/commit/95466fea852d16d2b7f13a09b1d1a84f9aac7bf9) feat: add albert-api to env example - [`aac3f55`](https://github.com/open-webui/open-webui/commit/aac3f55470cf8d3d10f4530b5674f8fe43577fbc) update docker compose to add albert api - [`1abc291`](https://github.com/open-webui/open-webui/commit/1abc29132f071e4db999e59eeeac98af0d5ee012) chore: add dsfr - [`ca72e03`](https://github.com/open-webui/open-webui/commit/ca72e03b6e39375bb42de17ab8fed2865bdcd7a2) init commit workflow - [`369bc2c`](https://github.com/open-webui/open-webui/commit/369bc2c3797438bac6b9345314f164e288d13503) add workflow - [`5a79379`](https://github.com/open-webui/open-webui/commit/5a79379ac1635fd5a5d3e8f512e378957c86d8b4) build and deploy on workflow branch - [`c602d7b`](https://github.com/open-webui/open-webui/commit/c602d7b2cef59b4a74f70998ffb99164ef08e773) update build & deploy ### 📊 Changes **15 files changed** (+83 additions, -1066 deletions) <details> <summary>View changed files</summary> 📝 `.env.example` (+3 -0) ➖ `.github/workflows/build-release.yml` (+0 -72) ➕ `.github/workflows/build_and_deploy.yml` (+65 -0) ➖ `.github/workflows/codespell.disabled` (+0 -25) ➖ `.github/workflows/deploy-to-hf-spaces.yml` (+0 -63) ➖ `.github/workflows/docker-build.yaml` (+0 -477) ➖ `.github/workflows/format-backend.yaml` (+0 -39) ➖ `.github/workflows/format-build-frontend.yaml` (+0 -57) ➖ `.github/workflows/integration-test.yml` (+0 -253) ➖ `.github/workflows/lint-backend.disabled` (+0 -27) ➖ `.github/workflows/lint-frontend.disabled` (+0 -21) ➖ `.github/workflows/release-pypi.yml` (+0 -32) 📝 `docker-compose.yaml` (+4 -0) 📝 `package-lock.json` (+10 -0) 📝 `package.json` (+1 -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 2026-04-20 04:02:50 -05:00

GiteaMirror closed this issue

2026-04-20 04:02:51 -05:00

GiteaMirror referenced this issue

2026-04-25 09:27:12 -05:00

[GH-ISSUE #22282] feat: utilize versioned prompts as custom model system prompts #35216

GiteaMirror referenced this issue

2026-05-05 23:00:15 -05:00

[GH-ISSUE #22282] feat: utilize versioned prompts as custom model system prompts #58353

Sign in to join this conversation.