Track GitHub PR activity and send only important alerts

OpenClaw checked 26 pull requests on a schedule, delivered updates to the author, and revealed a long-broken legacy script.

Done with OpenClaw· Intermediate

What they did
The author built a Python cron job around the gh CLI that runs every 5 minutes. It records each watched pull request’s current state in a saved JSON file, then notes any meaningful differences in a separate alert log. A second watchdog runs every 30 minutes, and OpenClaw wakes up on a heartbeat, verifies that watchdog, and forwards any waiting messages through Feishu.
How it went
The setup was watching 26 pull requests: 1 merged, 1 closed, and 24 still open. The watchdog also exposed a previous v2 script that had failed on its very first execution and never recovered over 18 days.
Tips
A single flat JSON store for alerts is brittle; if the heartbeat is missed, messages can be lost. A queue with webhooks would be a sturdier approach.

Try it yourself with OpenClaw

Keep an eye on my open pull requests in these GitHub repositories: [repo list]. On a 5-minute schedule, compare each PR against the last saved snapshot and flag anything I should know about, such as new comments, failing checks, merge conflicts, merges, or closures. When you find an update, draft a short message with the PR link and a brief explanation, then stop and ask before sending it to [chat app]. Don’t post comments, merge changes, close PRs, or push commits unless I approve first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on dev.to ↗

1 more report of this

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.