feature for developer marketing
Auto tweet GitHub commits that pass your filters, land as a human-approved build update on X, and keep noisy pushes out of your feed.
feature
TTP listens for GitHub push events and drafts a short, human-readable post in your voice from commit messages and metadata. The system can summarize multiple commits into a single build update so your feed stays focused on releases and milestones.
Every draft waits in one approval queue until a human approves, then publishes at each account's best time. To run this automation you must connect GitHub and an X account and grant the repository read and webhook permissions. The feature is available on our single plan; check account settings for posting and connected-account limits.
noise control
Focus posts on work that matters by filtering commits at the source. Define filters by branch, file path patterns, commit message regex, author, and tags so docs-only or automated CI commits stay out of the queue.
You can also group commits into release summaries and pull a build status link from your CI when available. Redaction rules remove secrets or internal URLs before a draft enters the approval queue, so the published update is safe for public channels.
approval workflow
Every draft is human-reviewed. The one approval queue gives your team a single place to edit voice, add context, and confirm links before publishing. You can require approval from specific roles or keep draft-only mode for testing.
The approval workflow is included on the single plan, but posting and connected-account limits apply. Platform rate limits and X content rules still govern what can be published. If compliance requires extra checks, add them as a pre-approval step in the queue.
setup and permissions
Connect GitHub using OAuth and enable a webhook for push events on the repositories you want to automate. Grant read and webhook permissions so TTP can parse commits and create drafts. Connect X via OAuth and grant posting permission for approved content.
TTP agents drive the automation and the auto SEO surface without requiring your platform API keys. If you prefer limited exposure, enable draft-only mode or restrict which repos can trigger drafts. Review plan details in account settings for posting limits and connected-account caps.
evaluate fit
Choose this automation if you need fewer, clearer updates from your engineering team and you want a human in the loop. It works best for teams with clear branch naming, release tags, or a CI status that can be linked in posts.
If your workflow generates many trivial commits or requires strict legal review before anything mentions builds, keep draft-only mode or use tight filters. For broader SEO or backlink tracking after a release, pair the workflow with TTP Get Found tools to monitor mentions and backlinks.
Questions for this workflow
TTP requires GitHub OAuth and a webhook on the repositories you choose so it can receive push events. For posting, connect an X account with OAuth and grant posting permission. No personal API keys are required to run TTP agents.
Use filters for branch, path, commit message patterns, author, and tags to stop noisy commits. Redaction rules strip secrets and internal links before a draft enters the approval queue. Every draft waits in one approval queue until a human approves.
Yes. Enable draft-only mode so drafts land in the approval queue and never publish automatically. You can also restrict which repositories or branches can trigger drafts while you refine filters.
Auto tweet GitHub commits is available on TTP's single, low plan. Posting and connected-account limits are set in your account plan details. Platform rate limits and X posting rules also apply and may affect throughput.
Start with the workflow above, keep the human review gate, and adapt the cadence to the accounts you actually operate.
Start a review-first workflow