[PR #341] [MERGED] allow custom intent in broadcast action without JSON #1275

Closed
opened 2026-05-07 01:01:20 +02:00 by BreizhHardware · 0 comments

📋 Pull Request Information

Original PR: https://github.com/binwiederhier/ntfy/pull/341
Author: @wunter8
Created: 6/22/2022
Status: Merged
Merged: 6/23/2022
Merged by: @binwiederhier

Base: mainHead: custom-intent-broadcast-action


📝 Commits (1)

  • ee38d76 allow custom intent in broadcast action without JSON

📊 Changes

2 files changed (+10 additions, -0 deletions)

View changed files

📝 server/actions.go (+2 -0)
📝 server/actions_test.go (+8 -0)

📄 Description

I noticed you could only change the intent of a broadcast action using the JSON publishing format. This allows you to specify the intent as a key/value pair in the Actions header


🔄 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/binwiederhier/ntfy/pull/341 **Author:** [@wunter8](https://github.com/wunter8) **Created:** 6/22/2022 **Status:** ✅ Merged **Merged:** 6/23/2022 **Merged by:** [@binwiederhier](https://github.com/binwiederhier) **Base:** `main` ← **Head:** `custom-intent-broadcast-action` --- ### 📝 Commits (1) - [`ee38d76`](https://github.com/binwiederhier/ntfy/commit/ee38d76bc2af354e4e6de1c6148bc9c7532265d1) allow custom intent in broadcast action without JSON ### 📊 Changes **2 files changed** (+10 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `server/actions.go` (+2 -0) 📝 `server/actions_test.go` (+8 -0) </details> ### 📄 Description I noticed you could only change the intent of a broadcast action using the JSON publishing format. This allows you to specify the intent as a key/value pair in the Actions header --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
BreizhHardware 2026-05-07 01:01:20 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#1275
No description provided.