Skip to content

Daily

See who starred or forked your GitHub repo

A daily email lists the usernames of everyone who starred or forked your repo since the day before.

Runs
Daily
Apps
GitHub
AI
Not needed
Access
Metadata: read

Send this to your assistant

Create a ClickRuntime automation: every day at 8am, email me the usernames of everyone who starred or forked acme/app since yesterday.

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

Stars and forks tell an open source maintainer whether a project is being noticed, but GitHub gives no useful digest of them. A launch post on Hacker News might add 300 stars in a day, or a fork might appear from a company that is about to build on your library, and you only find out if you happen to open the repository page at the right time.

Once a day the current list of stargazers and forks is fetched and compared with the set stored from the previous day. Anything new is written into an email: who starred, who forked and a link to each profile or fork. The stored set is then updated for tomorrow's comparison.

Maintainers, developer advocates and founders of developer tools use this to see who is paying attention without refreshing the page.

What you get out of it

  • You see who your users are

    Names beside each new fork often reveal real companies and contributors, which gives a maintainer someone to reach out to for feedback or sponsorship. Those are real leads for partnerships, sponsorship or user interviews that you would otherwise never see.

  • Launch spikes are traceable

    A sudden jump in stars on one date can be matched to the blog post or tweet that caused it, showing which channels send the most interested developers. You learn which of your launch efforts actually reached developers rather than guessing from analytics.

  • Forks flag potential contributors

    A fork is often the first step before a pull request, so noticing it early lets you welcome the person and point them to the contributing guide. Replying quickly to a fork owner often turns an observer into an active contributor.

  • A daily record needs no screenshots

    The emails form a dated history of growth and attention that you can cite in a funding application, sponsorship pitch or end-of-year project update. A simple archive like this beats trying to reconstruct growth from memory later.

  • Quiet days stay quiet

    Because only differences are reported, a day without new activity produces a small note rather than a long list, so the email stays easy to scan. That keeps the email worth opening every day, even on slow weeks.

How it works

What happens, step by step

  1. Every day, the automation reads the list of people who have starred or forked your GitHub repo.

  2. It compares the list with yesterday's to find the new names.

  3. You get an email with the usernames of new stars and forks, and how many of each.

Before it runs live

  • Connect GitHub

What you get

RunsDaily
See who starred or forked your GitHub repotoday, 9:00Succeeded
Email · acme/app: 12 new stars, 2 new forksStarred: devnorthwind, kchen, mlopez, … Forked: acme-labs, tpark

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.
fork_and_stargazer_monitor.pyexample
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

REPO = "acme/app"

def all_pages(path):
    users, page = [], 1
    while True:
        batch = gh("GET", path, params={"per_page": 100, "page": page})
        users += batch
        if len(batch) < 100:
            return users
        page += 1

@on_trigger
def run(event):
    stars = {u["login"] for u in all_pages(f"/repos/{REPO}/stargazers")}
    forks = {f["owner"]["login"] for f in all_pages(f"/repos/{REPO}/forks")}
    prev = state.get("seen")
    state.set("seen", {"stars": sorted(stars), "forks": sorted(forks)})
    if prev is None:
        return {"baseline": True}
    new_stars, new_forks = stars - set(prev["stars"]), forks - set(prev["forks"])
    if new_stars or new_forks:
        notify.email_me(f"{REPO}: {len(new_stars)} new stars, {len(new_forks)} new forks",
                        f"Starred: {', '.join(sorted(new_stars)) or 'none'}\nForked: {', '.join(sorted(new_forks)) or 'none'}")
    return {"stars": len(new_stars), "forks": len(new_forks)}

FAQ

Common questions

Can I watch several repositories at once?
Yes. List each repository and the email will group new stars and forks by repo. All of them use the same stored comparison set, so one email covers everything in a single daily message. The email shows each repo separately.
What happens when someone unstars a repository?
The comparison focuses on newly added stargazers and forks, so removals are not reported by default. If you want to know who left, ask for a section listing people in yesterday's set who are no longer there.
How many stargazers can it handle?
It pages through GitHub's stargazer list, so projects with large numbers are supported, though a very large repository takes longer per run. For huge repositories you can track just the count change instead of every name.
What permissions does it need?
Metadata: 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 (daily). 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 “See who starred or forked your GitHub repo” from your assistant

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