·Day 22 · building git-to-market in public

This week: better post gating and clearer LinkedIn previews

This week I focused on two things that make your public-build posts safer and more predictable: smarter post gates so you don't accidentally publish drafts, and clearer LinkedIn previews so the first dry-run looks like the real thing.

What shipped

  • Post-now gates: I added checks that stop a commit from turning into an immediate public post unless it passes simple truth checks. That means drafts, work-in-progress flags, and obvious placeholders won't become live posts by accident. The system still prepares the content, but it holds publishing behind these gates so you can review or schedule instead of surprising your audience.
  • LinkedIn dry-run truthfulness: Dry-run posts for LinkedIn now render more faithfully. When you do a preview or a test send, the title, excerpt, and image sizing match what will go live. This cuts the number of surprise edits after a real publish.
  • Error surfacing: When something blocks a post (a gate, a content mismatch, or an API hiccup), the dashboard now shows a clear explanation and suggested next steps. You won't have to hunt through logs to know why a post was held back.

Totals: 77 commits went into polishing these flows and fixing edge cases so daily publishing runs more reliably.

Why it matters

Accidental posts are the worst part of automating your public build. They cost trust and create cleanup work. These changes reduce that friction by making automated publishing predictable and reviewable. Better previews mean you make fewer manual tweaks after a post goes live, which keeps your weekly rhythm intact.

The clearer errors matter because they save time. Instead of guessing why a post didn't publish, you get an actionable message and can either fix the content or approve the queued post.

What's next

I'll follow this with two small pushes: one to make the gate rules editable per project, and another to add a single-click approve from the daily digest email. Both aim to keep automation useful without taking control away from you.

Related reading

  • Removed an old test alias so daily publishing runs reliably: https://gittomarket.io/w/gittomarket/removed-an-old-test-alias-so-daily-publishing-runs-reliably
  • Landing page now shows CMS content with a graceful fallback: https://gittomarket.io/w/gittomarket/landing-page-now-shows-cms-content-with-a-graceful-fallback
  • Landing page now shows CMS content with a graceful fallback: https://gittomarket.io/w/gittomarket/landing-page-now-shows-cms-content-with-a-graceful-fallback

Watch git-to-market ship, day by day

1 person is following the build

This week: better post gating and clearer LinkedIn…