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

This week: post-now gates and clearer LinkedIn dry-run truthfulness

This week we shipped clearer controls around "post now" behavior and made LinkedIn dry-runs more truthful so you can preview what will actually publish. The short version: fewer accidental posts, and previews that match reality. That matters if you build in public and want predictable, low-effort sharing from GitHub commits.

What shipped

  • A post-now gate that stops automatic posting when you explicitly want a hold. If you opt into a hold, git-to-market will queue the content instead of immediately publishing it. That prevents surprise posts after a late-night commit or a draft you didn't mean to push public.
  • LinkedIn dry-run previews were adjusted so the preview matches the final post more closely. The text, link handling, and image selection in the dry-run now reflect what LinkedIn will actually show when we post.
  • Error surfacing improvements: when a post fails (LinkedIn, X, Bluesky, or the blog), you'll get clearer messages about why it failed and what to do next. The system now distinguishes temporary platform hiccups from permanent permission issues.

Why it matters

Building in public only works if you can trust the system to represent your work accurately. Accidental posts are embarrassing and create work. Mismatched previews make you second-guess automated posting. And opaque failures mean you waste time guessing whether a post went out.

These changes reduce those risks. The post-now gate gives you an easy safety valve. Better dry-run truthfulness makes scheduling and approvals faster. Clearer errors get you back to shipping instead of debugging the publishing pipeline.

What's next

  • We’ll continue fine-tuning platform-specific previews so images and link previews line up across X, LinkedIn, and Bluesky. Expect fewer manual tweaks in your drafts.
  • We’re tracking a couple of edge cases where queued posts interact with manual edits; next sprint will focus on resolving merge-order confusion for queued content.
  • We’ll add a small dashboard indicator so you can see which posts are queued behind a post-now gate at a glance.

Related reading

  • This week: post-now gates and clearer LinkedIn dry-run truthfulness: https://gittomarket.io/w/gittomarket/this-week-post-now-gates-and-clearer-linkedin-dry-run-truthfulness
  • This week: post gates, clearer LinkedIn dry-run previews: https://gittomarket.io/w/gittomarket/this-week-post-gates-clearer-linkedin-dry-run-previews
  • This week: clearer LinkedIn previews and smarter post gates: https://gittomarket.io/w/gittomarket/this-week-clearer-linkedin-previews-and-smarter-post-gates-2

Watch git-to-market ship, day by day

1 person is following the build

This week: post-now gates and clearer LinkedIn dry-run…