Use case / use-case
Automatically toot GitHub releases to Mastodon on your own instance.
Turn each GitHub release into a Mastodon toot that respects the 500-character default, supports content warnings, and posts through your instance's API with a human approving first.
Fit the instance character limit
Most instances default to 500 characters, so S2P drafts a focused toot that names the shipped change and a link instead of pasting full release notes.
Honor content warnings
Many fediverse communities expect a content warning on promotional or long posts, so S2P can add a CW and keep the announcement collapsed by default.
Post to your own instance
S2P publishes through the Mastodon API with an access token from your instance, so your release toots stay on the server and handle you already use.
Channel fit
Mastodon is per-instance, and etiquette is local.
The fediverse is a network of independent servers with their own norms, so a release toot has to respect the local character limit, content-warning culture, and the fact that there is no central feed to game.
Authorize with an access token
S2P connects to your instance with a Mastodon API access token, so it posts as your account on the server you chose rather than a third-party relay.
Add a content warning when it fits
For longer or promotional updates, a content warning is the polite default on many servers, and S2P can apply one so the toot expands only when a reader opts in.
Respect the 500-character default
Some instances raise the limit, but 500 characters is the common default, so S2P leads with the shipped capability, the value, and a link.
Workflow
From GitHub release to a reviewed Mastodon toot.
Connect GitHub, authorize your instance, choose which releases deserve a toot, set your content-warning preference, then approve the draft before S2P publishes it.
- Trigger on the release types, repos, or tags worth a public toot.
- Draft inside the 500-character default and keep a link to the release.
- Apply a content warning automatically when your community expects one.
- Review and approve before the toot publishes to your instance.
- Keep the release, toot URL, and status together in one record.
Sample Mastodon toot
Shipped v2.4: approval rules now route each GitHub release to a reviewer before anything goes public. No more unreviewed launch posts. Notes and upgrade steps in the link.Keep exploring
Related pages
FAQ
Questions teams ask
Can S2P toot GitHub releases to Mastodon automatically?
Yes. S2P detects the release, drafts a toot within the instance limit, and publishes approved toots to your Mastodon account through the API.
Does S2P support content warnings on Mastodon?
Yes. You can set S2P to add a content warning so promotional or longer release toots stay collapsed until a reader chooses to expand them.
Which Mastodon instance does S2P post to?
The instance you authorize. S2P connects with a Mastodon API access token from your server, so it posts as your existing handle on that instance.
How does S2P handle the 500-character limit?
It drafts around the single most useful angle from the release and trims to fit the common 500-character default, keeping a version or link only when it adds credibility.
