Daily summary #1
Loading…
Reference in a new issue
No description provided.
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?
in my daily summary we should leave off the completed unless it is something unique from the recently added. don't show the queued section unless there is something queued.
last, i think the sunday message got truncated. we should split into multiple (numbered) messages to ensure all the info is recieved.
v0.5.2 deployed (commit
b23eb8b, plugin live in maubot — confirmed via/v1/plugins).Changes:
SeriesNamefor episodes) must appear as a substring of the release name. When some releases are still unique, only those are shown under a renamed header:✅ Also completed (not yet in Emby).(N/M)when there is more than one. The Sunday cleaner recap is the trigger case.Ready to verify — fire
!media digestin the notifications room. Today is Sunday 2026-05-03 so the cleaner block will exercise the chunking path.I think the Sunday daily summary should be split into two messages. The first message is the normal stuff the second for the deleted items. The second message would not need to call me by name since it's tagging right behind the first
v0.6.2 shipped (commit
87eef44, plugin live in maubot —version: 0.6.2, instance enabled+started).Change. On Sundays the emby-cleaner recap now ships as a second message after the main digest, instead of being appended to the same body and sharing byte-length
(N/M)chunking with it. Refactor:_send_digestbuildsdigest_lines(the standard daily content: recently added, completed, queued) and sends those first via a new_send_chunkedhelper.is_sundayand the cleaner recap is non-empty, it builds a separatecleanup_lineslist with its own**🧹 Weekly cleanup (emby-cleaner):**header and sends it as a second message._send_chunkedkeeps the existing byte-length chunking — but now applied per-message-group. So a long digest can still be split into(1/2, 2/2), and the cleanup recap is independently chunked. No(N/M)prefix when a group fits in a single chunk.The follow-up message has no daily-digest header / date, so it reads as a clean "and here's what got removed" addendum rather than a duplicate digest preamble. No user mention either way — neither the original digest nor the cleanup recap calls anyone by name.
Non-Sunday behavior unchanged.
I can't test the Sunday-only path until 2026-05-17 without forcing the
is_sundayflag, but the rest of the digest (today, Monday) sent fine. Closing — re-open if Sunday's run looks off.