Skip to main content
Analyses commits on the project’s tracked GitHub repositories and kicks off a background task that writes an announcement banner: the single most impactful user-facing change of the period as a headline (≤ 80 chars), a one-sentence body (≤ 160 chars), and a cta_label (≤ 24 chars). Returns immediately with a pending content record. Costs 25 credits. Publishing the draft (publish_content) makes it the project’s live banner, replacing the current one under the same embed key — the site’s snippet needs no change. Read it back with get_banner.

​
Arguments

​
Returns

Poll get_generation_status until the status is completed, then read the draft with get_content_draft. The draft is JSON (badge, headline, body, cta_label, link_url — an empty badge means none); edit it with update_content before publishing — banner drafts are validated and clamped on save (headline 80, body 160, cta_label 24, badge 16 characters; link_url an http(s) URL or null), and the draft’s badge becomes the prefill for a later regenerate.

​
Errors

  • No GitHub account connected. Connect GitHub in Sources first.
  • No active tracked repositories. Add repos in Sources first.
  • Invalid banner options: link_url must be an http(s) URL, expires_after_days one of 7, 14, or 30, and badge at most 16 characters.
  • Monthly credit limit reached (10/10 used). Upgrade your plan to keep generating content.

​
Example prompts

“Put a banner on our site about the biggest thing we shipped this week, linking to the changelog.”
“Generate a banner for the new API keys page, take it down after 14 days.”
“Banner for the beta of the new editor — tag it ‘Beta’ instead of ‘New’.”