·Day 22 · building git-to-market in public
This week: post-now gates and clearer LinkedIn dry-run truthfulness
This week I focused on two things that cut the anxiety of automatic posting: giving you an explicit gate before a post goes live, and making LinkedIn dry-runs honest about what will actually publish. Both changes are small to implement but important for people who want control while staying consistent.
What shipped
- –A post-now gate: when a commit generates a candidate post you can choose to publish immediately or hold it for review. The default automated flow still creates the draft, but the gate prevents accidental live posts and gives you a quick decision point.
- –LinkedIn dry-run improvements: dry-run previews for LinkedIn now reflect the true output the platform will receive. That means character counts, link handling, and basic formatting in the preview match what will be posted, so what you see in a dry-run is a faithful representation of the live post.
- –Better error surfacing: if a post fails to publish for any reason (API rate limits, auth issues, or platform rejections) you’ll get a clear, actionable error and a path to retry or hold the post. The system no longer silently drops a failed post.
Why it matters
People building in public want the discipline of regular posts without losing control. The post-now gate gives you that control: you can let daily posts run automatically, or step in for anything sensitive. It fits both hands-off and hands-on workflows.
LinkedIn is the platform where small differences in wording or links can change who sees your post. By making the dry-run truthful we reduce surprises and the need for last-minute edits. That saves time and protects your voice.
Finally, clearer errors mean less guesswork. When a post fails you won’t be left wondering whether the system tried and gave up. You can retry immediately or fix credentials and move on.
What's next
- –Improving the review UI so you can batch-approve or reject multiple candidate posts at once.
- –Adding a small audit trail showing why a held post was created (which commit and which repository), so you can decide faster during review.
- –Expanding truthful dry-runs to other platforms (X, Bluesky, and blog output) so previews are consistent everywhere.
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-3)
[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-2)
[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)
Watch git-to-market ship, day by day
1 person is following the build