mirror of
https://github.com/kuhyx/signal-bot.git
synced 2026-11-11 17:43:50 +01:00
Krzysztof kuhy Rudnicki
6c6d6d92de
Some checks are pending
CI / check (push) Waiting to run
Tomorrow's run would have posted four times into the same group: the day the bot owed from the catch-up, the week that closed inside it, today, and August's summary. Four notifications in one evening is how a daily tally becomes something people mute. They are blocks in a single message now, separated by a rule because Signal renders no markdown. That also makes the send atomic: the group gets all of it or none of it, and nothing is marked either way, where before a day was marked before its own weekly summary had even been attempted -- so a summary that failed was simply lost. The composition moved to reporting.py, both because bot.py hit the 250-line cap and because it is worth having pure: "what would the group be told?" is now answerable with no transport and no send. The closing-time caveat reads the clock instead of REPORT_HOUR. The scheduled run fires at the configured minute and still says exactly that; a run started by hand at some other hour now tells the truth rather than repeating a time nobody waited for. The 0.1.6 entry gains a bullet rather than taking a new version: no group has been told about 0.1.6 yet -- every one of them is still recorded at 0.1.5 -- so the release it describes has not happened from their side. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017w1HZ3cZ7neL3rFdQ6VMBA |
||
|---|---|---|
| .. | ||
| e2e_pack.py | ||
| gen_popes.py | ||
| preview_release.py | ||
| tagger.html | ||
| tagger.py | ||