Toutsu/GmRelayBot
1
1
Fork 0
Code Issues 18 Pull Requests 1 Actions Packages Projects Releases 85 Wiki Activity

feat(platform): route scheduler notifications through platform messenger #88

Closed
Toutsu wants to merge 0 commits from codex/issue-31-platform-messenger-scheduler into main
pull from: codex/issue-31-platform-messenger-scheduler
merge into: Toutsu:main
Conversation 0 Commits - Files Changed -
Toutsu commented 2026-05-21 12:31:46 +03:00
Owner
Copy Link
Copy Source

Closes #31

Summary

  • Moved scheduler, RSVP, confirmation and reminder flows into shared platform-aware services backed by IPlatformMessenger.
  • Added Telegram and Discord messenger implementations for confirmation requests, reminders, join-link notifications, direct session notifications and reschedule vote updates.
  • Registered shared scheduler/notification services in Telegram and Discord hosts, and bumped the project version to 2.7.0 across deployment/docs surfaces.

Tests

  • dotnet format --verify-no-changes --verbosity diagnostic
  • dotnet build
  • dotnet test tests/GmRelay.Bot.Tests/GmRelay.Bot.Tests.csproj --verbosity normal
  • Gitea Actions run #205 — success
  • Gitea Actions run #206 — deploy success

Merge

Merged via fallback local merge commit 3199c48fcd252a233845afa3206a3e9a14b5ccfd because Gitea did not allow self-approval merge through the PR endpoint.

Release: https://git.codeanddice.ru/Toutsu/GmRelayBot/releases/tag/v2.7.0

Closes #31 ## Summary - Moved scheduler, RSVP, confirmation and reminder flows into shared platform-aware services backed by IPlatformMessenger. - Added Telegram and Discord messenger implementations for confirmation requests, reminders, join-link notifications, direct session notifications and reschedule vote updates. - Registered shared scheduler/notification services in Telegram and Discord hosts, and bumped the project version to 2.7.0 across deployment/docs surfaces. ## Tests - dotnet format --verify-no-changes --verbosity diagnostic - dotnet build - dotnet test tests/GmRelay.Bot.Tests/GmRelay.Bot.Tests.csproj --verbosity normal - Gitea Actions run #205 — success - Gitea Actions run #206 — deploy success ## Merge Merged via fallback local merge commit `3199c48fcd252a233845afa3206a3e9a14b5ccfd` because Gitea did not allow self-approval merge through the PR endpoint. Release: https://git.codeanddice.ru/Toutsu/GmRelayBot/releases/tag/v2.7.0
Toutsu added 3 commits 2026-05-21 12:31:46 +03:00
docs: add issue 31 platform notification design 7426000937
docs: add issue 31 implementation plan 5dbec1a0a4
feat(platform): route scheduler notifications through platform messenger
PR Checks / test-and-build (pull_request) Successful in 7m9s
Details
2a707e4825
Toutsu closed this pull request 2026-05-21 12:51:21 +03:00
Some checks are pending
PR Checks / test-and-build (pull_request) Successful in 7m9s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area:bot
Telegram bot and worker logic
 area:data
Database schema, migrations and persistence model
 area:discord
Discord bot service and Discord adapter
 area:infra
Infrastructure, runtime and deployment
 area:miniapp
Telegram Mini App dashboard
 area:platform
Platform-neutral abstractions and adapter boundaries
 area:shared
Shared domain and rendering contracts
 area:web
Blazor web dashboard
 in-progress
В работе (issue взят агентом)
 next-up
Recommended immediate backlog
 pending-approval
Ждёт согласования плана решения
 platform:discord
Discord-specific behavior or adapter work
 platform:multi
Cross-platform or platform-neutral work
 platform:telegram
Telegram-specific behavior or adapter work
 priority:p0
Critical priority
 priority:p0
Блокирующий приоритет: задача должна быть выполнена до признания решения production-ready
 priority:p1
High priority
 priority:p2
Medium priority
 priority:p3
Lower priority
 security
Security-sensitive work
 type:bug
Bug fix or corrective work
 type:chore
Maintenance and supporting work
 type:feature
New product functionality
 type:refactor
Structural change without direct feature growth
 type:test
Testing and coverage work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Toutsu
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Toutsu/GmRelayBot#88
Delete Branch "codex/issue-31-platform-messenger-scheduler"

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?