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 #12177] [CLOSED] Feat/dynamic notification branding #9656

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

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/12177
Author: @JunaidPinjari
Created: 3/29/2025
Status: ❌ Closed

Base: dev ← Head: feat/dynamic-notification-branding

📝 Commits (2)

  • a805e03 Feat: Add optional ingest_file and as_attachment params to upload and download endpoints
  • ab5a4d5 Feat: Use WEBUI_NAME in notification titles for dynamic branding

📊 Changes

2 files changed (+42 additions, -39 deletions)

View changed files

📝 backend/open_webui/routers/files.py (+40 -37)
📝 src/routes/+layout.svelte (+2 -2)

📄 Description

  • Target branch: This pull request targets the dev branch.
  • Description: Replaces hardcoded "Open WebUI" in notification titles with the dynamic WEBUI_NAME value.
  • Changelog: Included below.
  • Testing: Manually tested in browser with notifications enabled.
  • Code review: Self-reviewed for consistency and correctness.
  • Prefix: feat

Changelog Entry

Description

Improves frontend flexibility by using WEBUI_NAME instead of the hardcoded "Open WebUI" in browser notification titles.

Changed

  • Notification titles now reflect the actual configured WEBUI_NAME, improving support for rebranded or self-hosted deployments.

Additional Information

This change affects:

  • Message notification titles (chat-related)
  • Channel event notifications

Dynamic naming improves user experience in customized or white-labeled environments.

🔄 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/12177 **Author:** [@JunaidPinjari](https://github.com/JunaidPinjari) **Created:** 3/29/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `feat/dynamic-notification-branding` --- ### 📝 Commits (2) - [`a805e03`](https://github.com/open-webui/open-webui/commit/a805e033a526fa559237d827e44c91511c6bb3c6) Feat: Add optional ingest_file and as_attachment params to upload and download endpoints - [`ab5a4d5`](https://github.com/open-webui/open-webui/commit/ab5a4d59520519816a5a2c4ee3c8a4658d4ca2e8) Feat: Use WEBUI_NAME in notification titles for dynamic branding ### 📊 Changes **2 files changed** (+42 additions, -39 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/routers/files.py` (+40 -37) 📝 `src/routes/+layout.svelte` (+2 -2) </details> ### 📄 Description - [x] **Target branch:** This pull request targets the `dev` branch. - [x] **Description:** Replaces hardcoded "Open WebUI" in notification titles with the dynamic `WEBUI_NAME` value. - [x] **Changelog:** Included below. - [x] **Testing:** Manually tested in browser with notifications enabled. - [x] **Code review:** Self-reviewed for consistency and correctness. - [x] **Prefix:** `feat` --- # Changelog Entry ### Description Improves frontend flexibility by using `WEBUI_NAME` instead of the hardcoded "Open WebUI" in browser notification titles. ### Changed - Notification titles now reflect the actual configured `WEBUI_NAME`, improving support for rebranded or self-hosted deployments. --- ### Additional Information This change affects: - Message notification titles (chat-related) - Channel event notifications Dynamic naming improves user experience in customized or white-labeled environments. --- <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:28:02 -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#9656
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?