On a schedule
Log daily engineering activity to a sheet
Each morning yesterday's merged pull requests and closed issues are added to a sheet, and a short summary is sent to you.
- Runs
- On a schedule
- Apps
- GitHub, Google Sheets
- AI
- Yes, uses the built-in AI allowance
- Access
- GitHub read; sheet editor
Send this to your assistant
Create a ClickRuntime automation: every morning, add yesterday's merged PRs and closed issues from our GitHub org to my Activity sheet, then email me a short AI summary.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An engineering manager reports progress to leadership every month and has to piece it together from GitHub searches across many repositories. Small but important wins are forgotten, and the report takes half a day.
A daily log in a sheet builds the record as the work happens. At month end, the manager filters the sheet instead of searching GitHub, and the daily summary keeps them aware of what shipped without reading every pull request.
What you get out of it
A complete record of what shipped
Every merged pull request and closed issue is logged with its date and repository. Nothing is forgotten when it is time to report.
Monthly reports from a filter
Filtering or charting the sheet gives the month's work in minutes. No more manual searches.
A daily summary in plain words
AI sums up the day's work in a few sentences. Managers stay informed without reading every title.
Shareable with non-engineers
Leadership and product teams can read the sheet without a GitHub account. Progress is visible across the company.
How it works
What happens, step by step
Every morning, ClickRuntime searches your GitHub organisation for pull requests merged and issues closed yesterday.
Each one is added as a row in your Activity sheet with date, repository, title, author and link.
AI writes a short summary of the day's work.
The summary is emailed to you.
Before it runs live
- Connect GitHub
- Connect your Google Sheets account and pick the spreadsheets it may use
What you get
Build your own
Need it to work differently?
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
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Slack
- Combine it with other GitHub and Google Sheets steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from clickruntime import on_trigger, credentials, http, notify, ai
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)
return resp.raise_for_status() or (resp.json() if resp.content else None)
ORG, SHEET_ID = "acme", "your-spreadsheet-id"
@on_trigger
def run(event):
day = date.today() - timedelta(days=1)
merged = gh("GET", "/search/issues", params={"q": f"org:{ORG} is:pr is:merged merged:{day}", "per_page": 100})["items"]
closed = gh("GET", "/search/issues", params={"q": f"org:{ORG} is:issue is:closed closed:{day}", "per_page": 100})["items"]
rows = [[str(day), kind, i["repository_url"].split("/")[-1], i["title"], i["user"]["login"], i["html_url"]]
for kind, items in (("PR", merged), ("Issue", closed)) for i in items]
if not rows:
return {"rows": 0}
sheets = build("sheets", "v4", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)
sheets.spreadsheets().values().append(spreadsheetId=SHEET_ID, range="Activity!A:F", valueInputOption="USER_ENTERED", body={"values": rows}).execute()
summary = ai.generate("\n".join(f"{r[1]} {r[2]}: {r[3]}" for r in rows)[:8000], max_output_tokens=200,
system="Summarise this day of engineering work in 3 plain sentences for a manager.").text
notify.email_me(f"Engineering activity {day:%a %d %b}: {len(merged)} merged, {len(closed)} closed", summary)
return {"rows": len(rows)}FAQ
Common questions
Which repositories does it include?
Can the summary go to Slack instead?
What columns does the sheet get?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Fill a timesheet sheet from your GitHub activity
Every Friday your timesheet sheet gets rows for the week's work, grouped by repository and day, with a short description and estimated hours.
See how it worksPublish blog posts from a topic sheet to your GitHub site
On your schedule, the next topic in your sheet becomes a blog post committed to your site's repository, and the row is marked done.
See how it worksTriage new GitHub issues and pull requests into a sheet
Every new issue and pull request is labelled by type and priority, logged in a triage sheet, and critical ones are posted to Slack.
See how it worksKeep exploring
Set up “Log daily engineering activity to a sheet” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.