Add buttondown_id to ep3 newsletter#410
Merged
Merged
Conversation
This is the canonical Buttondown email id for the ep3 newsletter that's already published. Backfilled manually because PR #409 fixed the auth issue going forward, but the newsletter workflow only runs on changes to blog/weekly/**, and there's nothing else triggering one right now. With this id committed, future Publish Newsletter runs will short-circuit on ep3 (publish_buttondown returns early when frontmatter has a buttondown_id) and not try to publish a 52nd duplicate draft. Co-Authored-By: Claude Opus 4.7 <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
2 participants
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.
Backfills
buttondown_id: em_1x79he62t38g09ph2xrsj43ecwonblog/weekly/20260407/index.md— the canonical Buttondown id for ep3, which is already published.PR #409 fixed the auth that was causing the workflow to fail to commit ids back. But the newsletter workflow only triggers on
blog/weekly/**changes, and there's no other push touching that path right now. So we'd be waiting on the next sync to flip ep3 over.With this id committed, future
Publish Newsletterruns short-circuit on ep3 (publish_buttondownreturns early when frontmatter already has abuttondown_id) instead of publishing a duplicate draft.Followup
🤖 Generated with Claude Code