This week: better post gates and clearer LinkedIn previews

This week I shipped tighter controls for which commits become public posts and cleaned up LinkedIn previews so what you see matches what readers will get. The goal is simple: fewer accidental posts, clearer previews, and faster error feedback so you can keep building in public without babysitting the publishing pipeline.

What shipped

• –Post-now gating: I added rules that stop a commit from becoming a public post until a simple, intentional signal is present. That means stray commits, WIP work, or experimental branches no longer turn into social posts by accident.
• –LinkedIn dry-run truthfulness: Preview generation for LinkedIn now runs the same content logic as the live publisher. The preview you see in the dashboard will match the live post’s text, image choice, and link formatting, reducing surprises when your post goes live.
• –Error surfacing: Publishing failures now surface immediately in the dashboard with a clear reason. Instead of a silent failure or a generic retry, you’ll see actionable messages so you can fix the commit or gating flag and re-run publishing quickly.

Why it matters

Building in public works best when it’s low-friction and low-risk. Automatic publishing saved time, but it also created anxiety: did I just post half-finished work? Did the LinkedIn preview truncate or lose the image? Those two worries are the top reasons people pause automation. The gates and truthful previews reduce both concerns. And when something still goes wrong, immediate error messages cut the time between noticing a problem and fixing it.

What I learned and what’s next

• –Conservative gating is the right default. Early tests showed users preferred an extra opt-in over silent publishing of drafts. I’ll keep the gate simple: a single flag you add to commits or a quick dashboard toggle.
• –Previews need to be exact. LinkedIn’s formatting quirks meant earlier previews were optimistic. Running the same renderer for dry-runs fixed most mismatches.
• –Next, I’ll polish the onboarding copy around gating so new projects don’t get stuck wondering why nothing posted. After that, I plan to add a lightweight audit log that shows which commits were gated and why, so teams can review decisions without digging through Git history.

Related reading

[This week: better post gating and clearer LinkedIn previews](https://gittomarket.io/w/gittomarket/this-week-better-post-gating-and-clearer-linkedin-previews)

[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-2)