chore(newsletter): mark issue-406 articles used and sync backlinks through 406 - #166
Merged
Merged
Conversation
…te pool Issue 406 is published, so its five articles (Part 1, Uber, Harness-Zero, the China framework PDF and the Jev talk) move from pool to used and stop resurfacing in future sourcing runs.
…h issue 406 Ran backlinks.mjs sync --all rather than --recent, because --recent always skips the newest issue and 406 has now been republished everywhere. Additive only, with no conflicts: 11 issues gain links (9 Substack, 2 LinkedIn, 4 Brevo), including the older 350-356 gaps. Issue 402 still has no LinkedIn article to match.
… 295 as URLs For unsent classic campaigns Brevo returns the sentence "Share link not available for classic campaigns which are not sent" in shareLink, and the --all sync wrote it into the syndication block, which the schema rejects as an invalid URL.
Skip a campaign whose shareLink is not a URL, so an unsent campaign's error sentence can no longer reach the frontmatter. A dry run of sync --all now changes nothing.
Visual parity — dark theme 🌙Every captured route is pixel-identical to the merge base across 1440x1000 (40 routes) and 420x900 (40 routes). Informational: label the PR |
Visual parity — light theme ☀️Every captured route is pixel-identical to the merge base across 1440x1000 (40 routes) and 420x900 (40 routes). Informational: label the PR |
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.
Post-publication housekeeping for issue 406: the five articles are marked as used in the candidate pool, and the syndication backlinks are synced now that the issue is live on Substack, LinkedIn and Brevo.
The backlinks sync ran with
--allrather than--recent 4, because--recentalways leaves out the newest issue (it's normally the one still being drafted), and 406 was the one that needed links. It added links only, with no conflicts, and also filled some older gaps: 14 issues gain links, 350-356 and 400-406.--allalso turned up a bug in the sync script. For campaigns that were never sent, Brevo puts an error sentence in the share-link field instead of a URL, and the sync wrote it into issues 258 and 295:The schema rejects that, so
npm run checkfailed on the first push of this branch. The last two commits revert those two entries and make the script skip any share link that isn'thttp(s). A dry run ofsync --allnow changes nothing, andnpm run checkpasses.One gap remains: issue 402 still has no LinkedIn link. The script couldn't find a LinkedIn article for it, so that one needs a manual lookup if it matters.