Skip to content

On a schedule

Get a morning digest of new pull requests

Each weekday morning you get one email with the pull requests opened in the last day, grouped by repo.

Runs
On a schedule
Apps
GitHub
AI
Not needed
Access
Pull requests: read

Send this to your assistant

Create a ClickRuntime automation: each weekday at 9am, email me the pull requests opened in acme/app and acme/api in the last day, grouped by repo, with the author and review status.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Engineering managers and tech leads who oversee several repositories have the same blind spot: pull requests opened overnight or over the weekend, scattered across five repos, with no single place that lists them. Reviews begin only after someone remembers to check each repository's Pull requests tab, and a PR that was opened Tuesday is still unreviewed on Friday.

Each morning the open PRs in each of your repositories are listed, and the ones created since the previous digest are kept. They are grouped by repository, with title, author and link, and sent as one email. If nothing new was opened, the digest is short, and nothing is missed between runs.

It suits managers of several repos, open source maintainers who check email before GitHub and teams that prefer a daily review routine.

What you get out of it

  • Review queue is known by 9am

    The morning list makes it easy to assign reviewers before standup, so new pull requests get attention on the day they are opened and not at the end of the week.

  • One email replaces five tabs

    A manager spread across multiple repositories saves the daily round of opening each Pull requests page, and the grouping by repo makes it clear where activity is happening. The grouping also makes it obvious which repository is getting all the activity.

  • Overnight work from other timezones

    Contributors in different timezones open PRs while you sleep, and the digest ensures their work is waiting on your list when you start, so they are not left idle. Contributors elsewhere stay productive because their work is seen early.

  • Nothing falls between digests

    Since the list covers everything created since the last digest, a PR opened at 11pm or on Sunday cannot be skipped by a time-of-day cutoff. Gaps and double reporting are avoided because the cutoff is the last digest, not a clock time.

  • Cadence builds review habits

    A predictable daily email nudges the team toward a regular review routine, which shortens the average time a pull request waits before a first response. Small habits like this compound across a quarter of releases.

How it works

What happens, step by step

  1. Every weekday at 9 am in your time zone, ClickRuntime checks your GitHub repos for open pull requests.

  2. It keeps the ones opened since the last digest.

  3. They are grouped by repo.

  4. You get one email listing each pull request with its author and how many reviewers were requested.

Before it runs live

  • Connect GitHub

What you get

RunsOn a schedule
Get a morning digest of new pull requeststoday, 9:00Succeeded
Email · New pull requestsacme/app #488 Add CSV export · kchen · 2 reviewers requested

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other GitHub steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
get_a_scheduled_digest_of_new_pull_requests.pyexample
from datetime import datetime, timedelta, timezone
from clickruntime import on_trigger, credentials, http, state, notify

def gh(method, path, **kw):
    resp = http.request(method, f"https://api.github.com{path}", headers={
        "Authorization": f"Bearer {credentials.connection('github', 'work')}",
        "Accept": "application/vnd.github+json"}, **kw)
    resp.raise_for_status()
    return resp.json() if resp.content else None

REPOS = ["acme/app", "acme/api"]

@on_trigger
def run(event):
    since = state.get("since") or (datetime.now(timezone.utc) - timedelta(days=1)).strftime("%Y-%m-%dT%H:%M:%SZ")
    sections = []
    for repo in REPOS:
        prs = [p for p in gh("GET", f"/repos/{repo}/pulls", params={"state": "open", "sort": "created",
               "direction": "desc", "per_page": 50}) if p["created_at"] > since]
        if prs:
            sections.append(f"{repo}\n" + "\n".join(
                f"  #{p['number']} {p['title']} · {p['user']['login']} · "
                f"{'draft' if p['draft'] else (str(len(p['requested_reviewers'])) + ' reviewers requested')}\n  {p['html_url']}"
                for p in prs))
    state.set("since", datetime.now(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ"))
    if sections:
        notify.email_me("New pull requests", "\n\n".join(sections))
    return {"repos_with_prs": len(sections)}

FAQ

Common questions

Does the digest include draft pull requests?
By default it lists open pull requests, and drafts count as open. If you prefer to leave drafts out until they are ready for review, ask for that and the digest will skip them. Add that rule at any time.
How are repositories chosen?
You name the repositories, or an organization to cover all of its repos. Each repo becomes a heading in the email. Adding a new repository later is a small change that you approve before it runs.
What if more than a few dozen PRs were opened?
The email lists all of them, grouped by repository, so a heavy day produces a longer message but nothing is cut off. If it becomes too long, you can limit the digest to certain labels or authors.
What permissions does it need?
Pull requests: read. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Get a morning digest of new pull requests” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.