Get GitHub release updates summarized and sent to Slack in Chinese

Watches GitHub repos for new releases, translates the notes to Chinese, and posts a summary to Slack.

How the work actually flows

It branches. Exactly one path is taken; runs once per each tracked github repository.

Pattern: Exclusive Choice (4) · Multiple Instances without Synchronization (12)

flowchart TD trig(["scheduled repository check"]):::trigtime s0[["Check each tracked repo"]]:::mi s1["Compare against last seen release"]:::task s2["AI summarizes release notes"]:::svc s3["AI translates to Chinese"]:::svc s4["Post summary to Slack"]:::task trig --> s0 s0 --> s1 s2 --> s3 s3 --> s4 gx{"× "}:::gate s1 --> gx p00["Continue to summarize"]:::task gx -->|"New release found"| p00 p10["End check"]:::task gx -->|"No new release"| p10 p00 --> s2 p10 --> s2 out[/"Chinese release summary in Slack"/]:::out pay{{"stays current without manual checking or translating"}}:::pay s4 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceRuns once per itemOne path onlyResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
Messaging & NotificationsTranslation & Localization
Connects
GitHubSlackGoogle GeminiRedis

The problem it solves

You want to know the moment a tool your team relies on ships a new release, but checking every repository by hand takes time you don't have. If your team reads Chinese, translating release notes yourself adds another step you'd rather skip.

Who it fits

Engineering or IT teams that track open-source tools and prefer updates in Chinese.

How it works

  1. On a set schedule, the system checks your chosen GitHub repositories for new releases
  2. It compares each release against the last one it saw so you never get a duplicate alert
  3. AI reads the release notes and summarizes the key points
  4. AI translates the summary into Chinese
  5. A formatted message is posted to your Slack channel
What you get

Release updates you never miss

You get new GitHub release notes summarized and translated into Chinese, posted straight to Slack.

What you get

A Slack message summarizing and translating each new release as soon as it's published.

What you need

A Slack account, a Google Gemini API key, and a Redis database for tracking releases.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook