Automated GitKraken Stale Branch Digest
Every morning, WebRun opens GitKraken, checks Workspaces for branches with no commits in the last 14 days, posts a digest to Slack showing the branch, owner, and how far behind main it is, and separately flags anything stale 30 days or more in Telegram so old branches get cleaned up instead of cluttering the repository indefinitely.
How do I find and clean up stale branches across my team?
WebRun checks GitKraken Workspaces every morning for branches with no commits in 14 days or more, posting a digest to Slack with each branch's owner and how far behind main it is. Branches stale 30 days or more also get flagged separately in Telegram, so old branches get cleaned up instead of piling up indefinitely.
- Stale branches get flagged before they clutter the repository
- The oldest, most abandoned branches stand out in their own channel
- Branch cleanup happens on a schedule instead of during a big spring clean
Built for engineering teams · platform teams · tech leads · software development teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.gitkraken.comin a real browser with your saved login - no setup, no API keys. -
1
GitKraken - check branches for staleness
gitkraken.com
WebRun opens GitKraken to check branches for staleness. - Open GitKraken Workspaces and list branches with no commits in the last 14 days
- Capture the branch owner and how far behind main it is
- Flag any branch stale for 30 days or more
Done when Every branch with no commits in 14 days or more is listed with its owner.
-
2
Slack - post the daily digest
slack.com
WebRun opens Slack to post the daily digest. - Post the day's stale branch digest to the team channel
- Show the owner and days behind main for each
- Note which ones are also being flagged in Telegram
Done when The team channel has today's stale branch digest.
-
3
Telegram - flag branches stale 30 days or more
telegram.org
WebRun opens Telegram to flag branches stale 30 days or more. - Send a separate cleanup flag for branches stale 30 days or more
- Name the branch and owner
- Skip branches within the 30 day window
Done when Every branch stale 30 days or more has a cleanup flag in Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete any branches?
No. WebRun only reports which branches look stale. Deleting a branch is always a decision your team makes directly.
Why separate the 30 day branches into Telegram?
So the oldest, most likely abandoned branches stand out instead of blending into the full daily digest.
What if a branch is meant to stay long term?
Exclude it from the stale check in GitKraken's own branch settings and it stops appearing on future digests.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.