fix/duty-week-rollover #1

Merged

kamash merged 2 commits from fix/duty-week-rollover into main

2026-08-19 15:20:49 +00:00

kamash commented

2026-08-19 15:20:40 +00:00

Owner

No description provided.

kamash added 2 commits 2026-08-19 15:20:41 +00:00

488f0b9a9b feat: ignore unknown commands instead of replying

The bot now answers only its predefined commands and stays silent on
anything else, logging ignored commands at debug level.

Tests no longer assert exact reply/reminder wording (which broke on
copy tweaks like 37a81a2) — they check behavior instead: message
counts, the names/handles substituted in, and that /sync persists its
fetch and doesn't leak internal errors.

e17aefb9e3 fix: assign duty weeks on their fetch-time tab across year rollover

Around New Year the empty-rota guard keeps the old year's cached rows
while resolveRange has already moved to the new year's tab, so an
auto-assignment could write an old-tab row index onto the new tab.
Stamp each DutyWeek with the tab it was fetched from and prefer it when
building the assignment range (clock fallback for pre-upgrade caches).

Also: widen the default fetch range to A1:G200 so a full year of rows
plus roster can't be silently truncated, add -race/golangci-lint/
govulncheck gates to CI (container pinned to 1.26.4-alpine), and add
.env.example documenting every configuration variable.

kamash merged commit bc3639f18c into main

2026-08-19 15:20:49 +00:00

kamash referenced this issue from a commit

2026-08-19 15:20:49 +00:00

Merge pull request 'fix/duty-week-rollover' (#1) from fix/duty-week-rollover into main

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kamash/dyzur-bot#1

No description provided.