Repository navigation
Add draft and publish workflows for broadcast and sequence emails - #186
Conversation
- Add draft editing, publishing, discarding, and email version history for broadcasts and sequences - Update API, SDK, dashboard, and documentation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3ff09da5aa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| patch.subject = subject ?? working.subject; | ||
| patch.content = (content ?? working.content) as any; | ||
| Object.assign(patch, noDraft); |
There was a problem hiding this comment.
When a sequence is paused after sends and an email is edited through this direct-save branch, the current subject and content are replaced without recording the version being displaced. The send path may already have created an email_content_versions row for that content, but with published_at still null; listEmailVersions filters out null timestamps and marks only the new current version, so the previously sent version disappears from history and cannot be restored. Record the prior live version before replacing it directly.
Useful? React with 👍 / 👎.
| content: email.draftContent, | ||
| }), | ||
| ]); | ||
| await db.transaction(async (tx) => { |
There was a problem hiding this comment.
When a request publishes multiple emails and another editor changes a later draft after the initial scan, that email's guarded update throws draft_changed after earlier loop iterations have already committed. The caller receives a failure even though some requested emails are live. Keep the multi-email updates and pin changes in one transaction, or otherwise prevent this partial-success outcome.
Useful? React with 👍 / 👎.
- Surface unpublished changes beside email content with publish and discard actions - Group version history and discard in an email actions menu - Align broadcast and sequence docs with the updated workflow
- Add MCP connection instructions to settings and promote assistants across empty states - Document dashboard setup and expose the configured MCP URL
Summary
Testing