Workflow
A controlled publishing loop from GitHub to social.
S2P is intentionally simple to operate: connect source events, define the rules, review generated drafts, then publish with traceability.
At a glance
The operating model.
The strongest setup is one repository, one brand profile, one trigger rule, and one social channel. Add automation after the loop is trusted.
Steps
The operating model.
Install the GitHub App
Authorize S2P for selected repositories so release activity can start the drafting workflow automatically.
Create trigger rules
Choose which releases, tags, branches, or labels should become social drafts and which should stay quiet.
Define the brand voice
Set tone, positioning, company description, hashtag policy, banned language, and channel-specific structure.
Review generated drafts
S2P drafts posts for each selected channel. Editors can compare variants, adjust copy, reject, regenerate, or approve.
Publish and measure
Approved posts publish through the relevant adapter. Status, external URLs, metrics, job runs, and audit entries stay attached.
Example
One release can create multiple channel-native drafts.
A technical release can become a concise X post, a fuller LinkedIn post, a Threads update, a Bluesky note, and a webhook update for your own publishing system.
Example release workflow
Release v2.4.0 ships in GitHub S2P matches the public launch rule Drafts are created for LinkedIn, X, Threads, and Bluesky An editor reviews and approves the final copy Approved posts publish with status and links attached
Next step
Start narrow, then scale.
The strongest setup is one repository, one brand profile, one trigger rule, and one social channel. Add automation after the loop is trusted.