Automated Tower Stale Branch Tracking
Every Monday, WebRun opens Tower, checks every repository for branches with no commits or merges in over two weeks, posts the full stale list to Slack, and pings Telegram for branches over a month old so they get closed out or merged.
How do I find and clean up stale Git branches automatically?
WebRun opens Tower every Monday and checks every tracked repository for branches with no commits or merges in over two weeks. It posts the full stale list to Slack grouped by repository and author, then pings Telegram for anything over a month old, so forgotten branches get merged, rebased, or deleted instead of piling up.
- Stale branches get flagged before they are forgotten for months
- Branch owners are pinged directly instead of a generic reminder
- Repositories stay tidy without a manual weekly audit
Built for Engineering managers · software teams · tech leads · solo developers
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
tower.imin a real browser with your saved login - no setup, no API keys. -
1
Tower - find stale branches
tower.im
WebRun opens Tower to find stale branches. - Open Tower and go through each tracked repository
- List branches with no commits or merges in the last two weeks
- Note the branch author and the days since last activity
Done when Every stale branch across your repositories is listed with its age.
-
2
Slack - post the stale branch list
slack.com
WebRun opens Slack to post the stale branch list. - Post the full stale branch list to the engineering channel
- Group branches by repository and author
Done when The team has this week's stale branch list in Slack.
-
3
Telegram - escalate the oldest branches
telegram.org
WebRun opens Telegram to escalate the oldest branches. - Send a short alert for branches untouched over a month
- Tag the branch author so they can merge, rebase, or delete it
Done when Branch owners have been pinged about anything over a month stale.
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 or merge branches on its own?
No. WebRun only lists stale branches and their owners. Merging, rebasing, or deleting a branch always stays a manual decision in Tower.
How old does a branch have to be before it is flagged?
Anything with no commits or merges in two weeks lands on the weekly Slack list, and anything over a month also gets a Telegram ping to the author.
Does it work across multiple repositories?
Yes. WebRun checks every repository you track in Tower and groups the stale branch list by repository so nothing is missed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.