Adam Moussa 7b2275a430 Post shift change notifications to the schedule channel (#21) (#22) ... Slash command handlers (drop, pick, swap) were posting notifications to command["channel_id"] — wherever the command was run. If someone ran /oncall drop from a DM, the notification went there instead of the schedule channel. Pickup buttons didn't have this problem because body["channel"]["id"] is always the channel where the button lives. Added SHIFT_CHANNEL_PARAM to the SlackBotFunction env vars, read it on cold start, and route all slash command shift-change notifications to the configured schedule channel. Closes #21		2026-05-01 14:15:56 -04:00
..
__init__.py	Initial commit: after-hours shift manager Slack bot	2026-04-03 18:32:32 -04:00
app.py	Post shift change notifications to the schedule channel (#21) (#22)	2026-05-01 14:15:56 -04:00
blocks.py	Fix weekly schedule starting from today instead of Monday (#18)	2026-04-08 13:36:34 -04:00
handler.py	Post shift change notifications to the schedule channel (#21) (#22)	2026-05-01 14:15:56 -04:00
roster_sync.py	Add force flag to roster sync DST guard	2026-04-07 18:46:26 -04:00
schedule.py	Fix race condition allowing multiple people to pick up the same shift (#19) (#20)	2026-05-01 14:09:39 -04:00
three_cx_client.py	Add 3CX roster sync Lambda with daily EventBridge trigger	2026-04-07 18:43:19 -04:00
weekly_post.py	Fix weekly schedule starting from today instead of Monday (#18)	2026-04-08 13:36:34 -04:00