Skip to content
ClickRuntime

Automate GitHub

Keep track of your repositories without watching GitHub all day. New issues and pull requests get flagged, triaged or reviewed, failed Actions runs reach you straight away, and release notes, backups and weekly repo stats happen on their own. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every night at 2am, download the JSON export from https://api.example.com/export, save each item as a file in the backups/ folder of my private repo acme/backups, commit only files that changed, and email me what changed.

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

Ideas

What you can automate in GitHub

Issues that get labelled and assigned, pull requests that get a first review, failed builds you hear about in minutes, and reports on your repos that arrive on schedule. These are ready-made starting points. Anything else you can describe works too.
Daily

Back up your data to a GitHub repo every night

Your exports and configs are committed to a private repo each night, only when something changed, with a summary by email.

See how it works
DailyAI

Refresh a generated file in your repo every day

A stats badge, data file or page in your repo is regenerated and committed once a day.

See how it works
Every 5 minutesAI

Get an AI review on every new pull request

Each new pull request gets a review comment within minutes, checked against your own guidelines.

See how it works
Weekly

Get weekly stats for your repos by email

Every Monday you see stars, forks, open issues and open pull requests for your repos, and how they changed since last week.

See how it works
Every 5 minutes

Assign new issues automatically

New issues get an owner based on their label, and anyone can take an issue by commenting /assign.

See how it works
On a scheduleAI

Write GitHub release notes from commits

When a new tag appears, readable release notes are written from the commits since the last tag and published on the release.

See how it works
Every 5 minutesAI

Label new issues and flag duplicates

New issues are labelled as a bug, feature or question, and likely duplicates get a comment pointing to the original.

See how it works
Every 5 minutes

Get a Slack message for every new issue

Each new issue on your repo shows up in Slack with its title, author and link.

See how it works
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.

See how it works
Every 5 minutes

Get pinged when a pull request is opened

You hear about each new pull request within minutes of it being opened.

See how it works
Hourly

Hear about new releases of repos you follow

When a project you depend on ships a release, you get the version and release notes.

See how it works
Weekly

Label and close stale issues every week

Issues with no activity for 60 days are labelled stale, closed 14 days later if nothing happens, and you get the list.

See how it works
On a schedule

See pull requests waiting for your review

Each weekday morning you get a list of pull requests where your review is requested, with how long each has waited.

See how it works
On a schedule

Get your GitHub notifications in one email

Twice a day you get one email of your unread GitHub notifications, grouped by repo, instead of dozens.

See how it works
Every 5 minutes

Get alerted when a build fails on main

When a GitHub Actions run fails on main, you get a Slack message with the link within minutes.

See how it works
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.

See how it works
Weekly

See who starred a GitHub repo, with profiles

Every Monday a CSV of all stargazers of a GitHub repo arrives by email, with the star date, name, company, location and follower count.

See how it works
The moment it happens

Update CHANGELOG.md when a GitHub release is published

When a GitHub release is published, its notes are added to the top of CHANGELOG.md in the repo with a commit.

See how it works
The moment it happensAI

Ask for missing details on new GitHub issues

New GitHub issues without steps to reproduce or a version number get a polite comment asking for them and a needs-info label.

See how it works
Weekly

Get a weekly list of GitHub issues with no reply

Every Monday an email lists open GitHub issues where no maintainer has commented yet, oldest first, with how many days each has waited.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with GitHub, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any GitHub automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what GitHub should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

When a new issue is opened in my GitHub repo, use AI to add a bug, feature or question label and comment asking for steps to reproduce if a bug report has none.

Every morning at 9, post open GitHub pull requests waiting for review for more than 2 days to #engineering on Slack.

Every Friday, collect merged GitHub pull requests from this week, add them to my Releases sheet in Google Sheets, and email an AI-written changelog to the team through Gmail.

Works with

GitHub with the apps you already use

Most of what happens in GitHub matters to people who don't live in it. Connect it to where your team talks, plans and keeps records, so issues, releases and builds reach them there.

GitHub works with hundreds of other apps

Name any of them when you ask your assistant, and your automation connects them. Over 248 apps are ready to go, and anything with an API works too.

  • GitLab
  • Linear
  • Discord
  • Microsoft Teams
  • Sentry
  • Vercel
  • Netlify
  • Cloudflare
  • PagerDuty
  • Datadog
  • CircleCI
  • Confluence
  • Trello
  • Asana
  • Airtable
  • Google Drive
  • OpenAI
  • Supabase

Beyond chat

Have GitHub work when you're not in the chat

Connecting GitHub to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect GitHub

You connect GitHub with a fine-grained personal access token that you create yourself. You choose which repositories it can reach and what it can do in them.

GitHub

Developer / Source control

  1. In GitHub, open your profile picture, then Settings, Developer settings, Personal access tokens, Fine-grained tokens, and choose Generate new token.
  2. Give it a name and an expiration, and choose the resource owner (you or your organization).
  3. Under repository access, pick only the repos the automation needs, then set the minimum permissions, such as Issues, Pull requests or Contents.
  4. Generate the token and copy it.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for GitHub.

Good to know

GitHub limits that affect automations

  • Fine-grained tokens expire after 30 days by default. You can choose 1 to 366 days or no expiry, unless your organization sets a maximum, so plan to replace the token before it runs out.
  • Organizations can require approval before a fine-grained token can access their repositories. The automation can't reach them until an owner approves it.
  • GitHub removes tokens that have not been used for a year.
  • Fine-grained tokens can't read your GitHub notifications. A notifications digest needs a classic token with the notifications scope.
  • Watching for new issues, pull requests and failed runs works by checking every few minutes, since repo webhooks need admin setup that a personal token doesn't cover.

FAQ

Questions about automating GitHub

What can ClickRuntime see in my GitHub?
Only the repositories you selected when you created the token, with the permissions you gave it. With read access it can list issues, pull requests, releases, Actions runs, stars and forks. With write access it can label, assign, comment on and close issues, commit files and publish releases.
How fast will I hear about a new issue or pull request?
Within about 5 minutes. The automation checks your repo on a schedule and only posts items it hasn't seen before.
Can it review pull requests?
Yes. It can read the changed files of each new pull request, have AI review them against your guidelines and post the review as a comment. Very large diffs are cut down before review.
Do I need AI for GitHub automations?
No. Alerts, digests, stale issue clean-up, auto-assigning and repo stats run without it. Pull request reviews, issue triage and release notes use the AI that comes with every ClickRuntime plan, so you don't need your own AI key.
Can it watch public repos I don't own?
Yes, for things like new releases. Reading releases of a public repo needs no repository permission on your token.
Is this a GitHub connector for ChatGPT or Claude?
Not for chatting with GitHub data. A chat connector lets your assistant read and change GitHub while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each GitHub event.

Related pages

Keep exploring

Tell your assistant what GitHub should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude