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

chore: add platform identity and platform_messages for multi-platform support (#23) #79

Closed
Toutsu wants to merge 0 commits from feature/issue-23-platform-identity into main
pull from: feature/issue-23-platform-identity
merge into: Toutsu:main
Conversation 1 Commits - Files Changed -
Toutsu commented 2026-05-15 10:16:40 +03:00
Owner
Copy Link
Copy Source

Summary

Changes

  • V016__add_platform_identity.sql:
    • players: platform, external_user_id, external_username
    • game_groups: platform, external_group_id, external_channel_id
    • platform_messages table для кросс-платформенного трекинга сообщений
    • Backfill всех существующих Telegram-данных в новые колонки
    • Пересоздана get_group_attendance_stats с COALESCE(external_username, telegram_username)
  • V012__add_attendance_stats.sql: использует COALESCE(external_username, telegram_username)
  • CreateSessionHandler: dual-write в legacy и новые identity-колонки
  • JoinSessionHandler: чтение/запись platform identity в новом формате
  • PlatformIdentityMigrationTests (7 smoke tests)
  • Версия синхронизирована: Directory.Build.props, compose.yaml, deploy.yml, NavMenu.razor → 2.0.0

Test plan

  • dotnet build — локально на main, 0 warnings / 0 errors
  • dotnet test — локально на main, 145/145 passed
  • dotnet format GM-Relay.slnx --verify-no-changes — локально, clean
  • dotnet restore GM-Relay.slnx --locked-mode — локально, success
  • PR CI: Gitea Actions run #181 — success
  • Deploy main: Gitea Actions run #182 — success

Workflow

  • Issue resolved and linked
  • All 4 version files synchronized to 2.0.0
  • CI passes (#181)
  • Review/merge path handled: self-approval is blocked by Gitea, merge API returns 405 because PR head is already included in main
  • Integrated into main via merge commit 7cecb72
  • Deployed via main (#182)
  • Release published: v2.0.0
  • Issue #23 closed with release reference

Closes #23

## Summary - Подготовка схемы БД к мультиплатформенности (Discord и др.) - Issue #23 - PR уже интегрирован в `main` merge-коммитом `7cecb72`, где `11b145a` является вторым parent. ## Changes - V016__add_platform_identity.sql: - `players`: `platform`, `external_user_id`, `external_username` - `game_groups`: `platform`, `external_group_id`, `external_channel_id` - `platform_messages` table для кросс-платформенного трекинга сообщений - Backfill всех существующих Telegram-данных в новые колонки - Пересоздана `get_group_attendance_stats` с `COALESCE(external_username, telegram_username)` - V012__add_attendance_stats.sql: использует `COALESCE(external_username, telegram_username)` - CreateSessionHandler: dual-write в legacy и новые identity-колонки - JoinSessionHandler: чтение/запись platform identity в новом формате - PlatformIdentityMigrationTests (7 smoke tests) - Версия синхронизирована: `Directory.Build.props`, `compose.yaml`, `deploy.yml`, `NavMenu.razor` → **2.0.0** ## Test plan - [x] `dotnet build` — локально на `main`, 0 warnings / 0 errors - [x] `dotnet test` — локально на `main`, 145/145 passed - [x] `dotnet format GM-Relay.slnx --verify-no-changes` — локально, clean - [x] `dotnet restore GM-Relay.slnx --locked-mode` — локально, success - [x] PR CI: Gitea Actions run #181 — success - [x] Deploy `main`: Gitea Actions run #182 — success ## Workflow - [x] Issue resolved and linked - [x] All 4 version files synchronized to `2.0.0` - [x] CI passes (#181) - [x] Review/merge path handled: self-approval is blocked by Gitea, merge API returns 405 because PR head is already included in `main` - [x] Integrated into `main` via merge commit `7cecb72` - [x] Deployed via `main` (#182) - [x] Release published: [v2.0.0](https://git.codeanddice.ru/Toutsu/GmRelayBot/releases/tag/v2.0.0) - [x] Issue #23 closed with release reference Closes #23
Toutsu added 2 commits 2026-05-15 10:16:40 +03:00
feat: add health check endpoints for Bot and Web
PR Checks / test-and-build (pull_request) Successful in 8m53s
Details
3bea327043 
- Web: add /health endpoint with PostgreSQL readiness check (returns 200+JSON or 503)
- Web: add /alive endpoint for liveness probe
- Bot: add BotHealthCheckHostedService serving /health on port 8081 via HttpListener
- Bot: expose port 8081 in Dockerfile and install wget for healthcheck
- compose.yaml: add healthcheck sections for bot and web services
- tests: add TDD tests for both health endpoints

Bump version -> 1.16.0

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
fix: address review feedback for health check endpoints
PR Checks / test-and-build (pull_request) Successful in 8m34s
Details
105b3c59d7 
- Install wget in Web Dockerfile for compose healthcheck
- Ensure HttpListener response is always closed in BotHealthCheckHostedService
- Use ephemeral port in Bot health check test to avoid port conflicts
- Rename NpgsqlHealthCheck test to reflect actual behavior

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Toutsu added 1 commit 2026-05-15 10:48:32 +03:00
chore: add platform identity and platform_messages for multi-platform support (#23)
PR Checks / test-and-build (pull_request) Successful in 9m36s
Details
11b145a967 
TDD cycle for issue #23:
- RED: 9 migration smoke tests (file presence + schema expectations)
- GREEN: V016 migration adding platform identity columns
- GREEN: CreateSessionHandler, JoinSessionHandler, Web SessionService updated
  with dual-write to legacy and new identity columns + COALESCE fallbacks
- GREEN: get_group_attendance_stats recreated for external_username
- Bump version to 2.0.0

Changes:
- V016__add_platform_identity.sql:
  - players: platform, external_user_id, external_username
  - game_groups: platform, external_group_id, external_channel_id
  - platform_messages table with cross-platform message tracking
  - Backfill all existing Telegram data into new columns
  - Recreate get_group_attendance_stats with COALESCE fallback
- V012__add_attendance_stats.sql: use COALESCE(external_username, telegram_username)
- CreateSessionHandler: dual-write + COALESCE fallbacks in SELECTs
- JoinSessionHandler: dual-write to new identity columns
- Web SessionService: dual-write to new identity columns
- PlatformIdentityMigrationTests (9 smoke tests covering all handlers)
- Version synced: Directory.Build.props, compose.yaml, deploy.yml, NavMenu.razor → 2.0.0

Legacy telegram_* columns preserved for backward compatibility.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Toutsu force-pushed feature/issue-23-platform-identity from ae20bfb4d2 to 11b145a967 2026-05-15 10:48:32 +03:00 Compare
Toutsu commented 2026-05-15 12:00:48 +03:00
Author
Owner
Copy Link
Copy Source

Workflow cleanup:

  • PR head 11b145a is already included in main as the second parent of merge commit 7cecb72.
  • Diff against main is empty.
  • Version files are synchronized at 2.0.0.
  • PR CI run #181 — success.
  • Deploy run #182 — success.
  • Release published: v2.0.0.

Gitea blocks self-approval (approve your own pull is not allowed) and merge API returns HTTP 405 because this PR is already integrated, so closing it as completed.

Workflow cleanup: - PR head `11b145a` is already included in `main` as the second parent of merge commit `7cecb72`. - Diff against `main` is empty. - Version files are synchronized at `2.0.0`. - PR CI run #181 — success. - Deploy run #182 — success. - Release published: [v2.0.0](https://git.codeanddice.ru/Toutsu/GmRelayBot/releases/tag/v2.0.0). Gitea blocks self-approval (`approve your own pull is not allowed`) and merge API returns HTTP 405 because this PR is already integrated, so closing it as completed.
Toutsu closed this pull request 2026-05-15 12:00:49 +03:00
Some checks are pending
PR Checks / test-and-build (pull_request) Successful in 9m36s
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#79
Delete Branch "feature/issue-23-platform-identity"

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?