newsletter-prep: draft the next campaign issue automatically - #16
Merged
Merged
Conversation
… the test copy Gathers every blog post and release since the previous issue, drafts from that material only, checks every link and drops the dead ones, creates the issue in myna with its A/B design and mails one test copy. It stops before the send on purpose. The first automatic draft put a 21+ cigar post in a newsletter to every customer, found by the exclusion list rather than by the writing, and the earlier hand-made draft carried a 404 install link that only a check caught. A person reads the test copy, then the daemon sends it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…nd wrap up at the end 003 and 004 name a set an earlier issue decides, so the run fell back to default and says so rather than dying on the day. When no sends are left, the last run mails the campaign's numbers instead of going quiet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Each run marks off whatever myna has actually sent and tops the plan up, so there is always a future issue on the books. Without the reconciliation step the plan's sent flags never flipped, the same issue stayed next forever and the schedule stalled after one send. A recurring block sets the cadence; --plan runs it against a copy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Companion to #15. Drafts the next issue three days out and mails a test copy, so the only manual step left is reading it.
--cta-setfrom the plan) and sends one test copy.myna-daemonsends it at its hour, so nothing else is needed.Why it stops at the test copy. The first fully automatic draft pulled a 21+ cigar post into a newsletter aimed at every customer. That is what
EXCLUDE_WORDSnow catches, but it is also why the last step is a person. The earlier hand-written draft had a 404 install link in it too, caught only by checking.Installed on dev, daily at 06:00 UTC, alongside the #15 digest at 05:25. Both cron lines carry a note to delete them when the month ends.
🤖 Generated with Claude Code