t.behrendt/realDynDNS
1
0
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Releases Activity

feat: notification provider #8

Merged
t.behrendt merged 4 commits from feat-notification-provider into main 2024-08-11 11:52:52 +02:00
Conversation 0 Commits 4 Files Changed 11 +304 -31
t.behrendt commented 2024-08-11 10:17:32 +02:00
Owner
Copy Link
No description provided.
t.behrendt added 4 commits 2024-08-11 10:17:32 +02:00
feat: add notification provider 12898535e6
feat: notification provider gotify 9749d4a28d
docs: document notification provider config 2bbc33dcb4
docs: document gotify notification provider config
All checks were successful
CI / test (pull_request) Successful in 37s
Details
210caefadd
t.behrendt merged commit 7bb1e9ca08 into main 2024-08-11 11:52:52 +02:00
t.behrendt deleted branch feat-notification-provider 2024-08-11 11:52:52 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot trivy-bot t.behrendt
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/realDynDNS#8
Delete Branch "feat-notification-provider"

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?