What a run commits
Commits are attributed to the application bot. No files are changed relative to the selected parent commit.
One labelled empty commit per local day
A quiet heartbeat for the repositories you choose.
Schedule one clearly labelled empty commit on a branch you already own. See exactly what happened, and pause, resume or remove it at any time. A heartbeat, not a contribution streak.
Starts paused · Nothing is published without your explicit consent
Overview
Dashboard
GitHub App connected · consent recorded for 1 automation
Automations
2 configured
you/field-notes
mainDaily 09:00 · Europe/London
Next run Tomorrow, 09:00Run todayPause
you/dotfiles
trunkDaily 21:30 · Asia/Kolkata
Next run Not scheduledResume
Today's slot · you/field-notes
Published09:02 local
00:0009:0024:00
Commit preview
chore: automated daily heartbeat
make-a-commit[bot] · 0 files changed
Recent runs
View history
- Today 09:02you/field-notesPublisheda1c9e42
- Yesterday 21:31you/dotfilesSkipped—
- Yesterday 09:01you/field-notesPublished7f03b1d
- Thu 09:04you/field-notesPublishede58d0c7
- Empty commits only
- Existing branches only
- Bot-attributed
- One per local day
- Pause any time
- Identity-only sign-in
Why make-a-commitBuilt to do one thing,
Built to do one thing,
carefully.
No frequency tricks, no backdating, no identity spoofing. One empty commit a day on a branch you already own, with every state shown honestly.
One slot per local day. Never backdated.
Runs are scheduled approximately at your selected local time. Delays and failures are shown in history.
- Pick an existing branch and a five-minute daily time in your own timezone.
- Schedule edits start after the current day ends, and you see the next eligible run before saving.
- Run today reuses today's slot. It never adds an extra commit.
How it works
From sign-in to first commit, in three steps.
Identity, repository access and the schedule are three separate, explicit decisions, so you always know what you granted.
- Step 1
Sign in with GitHub
Sign-in establishes your account identity only. It never receives repository scopes.
- Step 2
Install the app where you choose
A separate GitHub App installation grants access to the personally owned repositories you select, and nothing else.
- Step 3
Pick a branch and a daily time
Choose an existing branch and a local time, then give consent. The app never creates a branch and never force-updates one.
Safeguards
The fine print, in large print.
Everything the app does to your repositories, stated before you enable anything.
Continuous integration
A commit may trigger your repository's workflows or deployments even when no files change.
Review your workflow triggers before enabling an automation on a branch that deploys.
Repositories you choose
Connect the GitHub App to repositories you choose. GitHub's Contents permission allows more than empty commits; this app restricts itself to the automation described here.
Identity only at sign-in
GitHub sign-in establishes your account identity only. Repository access is a separate, explicit GitHub App installation step — the login never receives repository scopes.
Not a contribution streak
Bot commits do not guarantee activity on your personal contribution graph. GitHub decides what counts towards the graph.
FAQ
Questions worth answering first.
Short answers in the same plain language the app uses before you enable anything.
What exactly does a run do?
Commits are attributed to the application bot. No files are changed relative to the selected parent commit.
Can this trigger my CI?
A commit may trigger your repository's workflows or deployments even when no files change. Review your workflow triggers before enabling an automation on a branch that deploys.
Will it fill in my contribution graph?
Bot commits do not guarantee activity on your personal contribution graph. GitHub decides what counts towards the graph, and bot-authored commits are attributed to the app.
How precise is the daily time?
Runs are scheduled approximately at your selected local time. Delays and failures are shown in history.
Do I need a separate sign-up?
No. Your account is created the first time you continue with GitHub. Repository access is a separate GitHub App installation you control.
How do I stop it?
Stops future work. A request already sent to GitHub may still complete. Removing an automation or deleting your account stops future work as well; your application settings and history will be removed after active work stops. Existing GitHub commits remain. The GitHub App is not automatically uninstalled.
Get started
Ready when you are.
Sign in, review the disclosures, install the GitHub App on the repositories you pick, and schedule your first daily commit. Nothing is published until you give explicit consent.