Skip to content

Back-to-back calls no longer inherit the previous call's name - #35

Merged
tommusrhodus merged 2 commits into
a8cteam51:trunkfrom
tijosh:call-name-fix
Nov 18, 2026
Merged

tommusrhodus merged 2 commits into
a8cteam51:trunkfrom
tijosh:call-name-fix

Conversation

@tijosh

@tijosh tijosh commented Nov 18, 2026

Copy link
Copy Markdown

When a call finishes early and another starts while its calendar slot is still running (a quick debrief straight after, say), Oatcake noticed the second call and named it after the first: same title, same folder, same invite. So Who's who offered the first call's invitees for the debrief, and the sidebar showed two meetings with the same name.

Now, when Oatcake notices a call by itself and the event happening now already has a recording, the new recording is just "Call", with no event attached. This covers the "On a call?" notification's text, its Record button, and clicking it (New recording). An event counts as recorded if it was recorded since launch or still has a recording in Needs review.

Nothing else changes. The event is picked exactly as before, including the ten minutes before it starts. Starting a recording from the event itself (New recording, Upcoming) isn't affected.

Known trade-off: leave a call and rejoin the same meeting, and the second recording is "Call" rather than the meeting's title.

Tested

  • swift test: 96 tests pass, including a new one (callAfterAnEarlyFinish) for the old results when nothing's been recorded and "no event" once it has.
  • Against a real morning's calendar and recordings: a 09:00–10:00 event recorded from 09:01 to 09:47, then a call at 09:47. The old rule named the second call after the 09:00 event. The new one gives no event, and still gives none for a call from 09:50, when the next event's ten minutes would start.

Not tested

  • A live back-to-back call in a built copy.

🤖 Generated with Claude Code

A call that finished early and was followed by another in its slot (a
quick debrief, say) was named after the first call, filed in its folder
and given its invite. When Oatcake notices a call by itself and the event
happening now has already been recorded, the recording is now just
"Call". Everything else about picking the event is unchanged, as is
starting a recording from the event itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tijosh tijosh changed the title A call noticed after its event was already recorded isn't named after that event Back-to-back calls no longer inherit the previous call's name Nov 18, 2026
eventHappening had gone in between ignoredEvent and the comment that describes it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@tommusrhodus
tommusrhodus merged commit 6bdf152 into a8cteam51:trunk Nov 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants