seahaven-openswe[bot] 612572bde7 Reuse weekly schedule post instead of reposting ... The Monday rollover deleted last week's schedule message and posted a fresh one every week, which re-notified the channel, changed the permalink, and dropped any thread/reactions. Roll the two-week window forward by editing the stored message in place (the same chat_update path in-week shift changes already use), falling back to a fresh, pinned post on first run or when the edit fails. A native pin keeps it reachable from the channel header now that it no longer rises on the weekly repost. Records the evaluation behind this in docs/sticky-schedule-post.md. Refs: #135		2026-06-26 19:33:05 +00:00
..
app.py	[#134] Clarify dropping a shift and differentiate night rows (#138)	2026-06-26 15:19:22 -04:00
CHANGELOG.md	Reuse weekly schedule post instead of reposting	2026-06-26 19:33:05 +00:00
handler.py	Merge ring-scheduler-3cx and resolve all open issues (#62)	2026-05-12 19:55:39 -04:00
requirements.txt	Update boto3 requirement from >=1.43.31 to >=1.43.36 in /src/slack-bot (#131)	2026-06-24 00:49:22 +00:00