Repository navigation
Conversation
Calendar rows were deduplicated on their start time alone. Of two different events starting at the same minute, such as two all-day events on one day or meetings from two imported calendars, only one was kept as soon as a calendar was imported again, a second one was added, or any time had been logged by hand. The other event's hours silently went missing from timesheets, invoices and Planned. A re-imported event now replaces its earlier copy only when start, end, all-day, title and tag all match. Neither calendar source gives Tuttle an event id, so an event whose title or times changed sits next to its old copy instead of replacing it. Syncing a system calendar replaces all of its rows, which clears such copies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
clstaudt
added this pull request to stack #634
October 18, 2026 20:24
clstaudt
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging calendar events kept only one of several events that start at the same minute, so tracked hours vanished from timesheets, invoices and Planned. It happened on re-imports, when adding a second calendar, and for anyone with a manual entry.
An earlier event is now replaced only by a new one that matches it entirely: start, end, duration, all-day, title, tag and source. Re-importing stays idempotent. Neither calendar source gives Tuttle an event id, so an event whose title or times changed appears next to its old copy: visible, rather than lost.
馃 Generated with Claude Code