Automated Codeberg Stale Pull Request Digest
Every morning, WebRun opens Codeberg, reviews open pull requests across your repositories, posts a Telegram digest of any waiting more than five days for review, and sends a text for anything waiting more than two weeks so genuinely stuck contributions do not get missed.
How do I stop pull requests from going stale on Codeberg?
WebRun reviews open Codeberg pull requests every morning, posting a Telegram digest of any waiting more than five days for review. Anything still waiting after two weeks also gets a direct text to the maintainer, so routine review lag stays visible in the daily digest while genuinely stuck pull requests get a harder nudge.
- Stale pull requests show up in a daily digest instead of scrolling out of view
- Genuinely stuck contributions get a direct text after two weeks
- Contributors get a faster response because nothing sits forgotten
Built for Open source maintainers · small engineering teams · self-hosted Git users · community project leads
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
codeberg.org/user/loginin a real browser with your saved login - no setup, no API keys. -
1
Codeberg - review open pull requests
- Open Codeberg and review open pull requests across your repositories
- Check how many days each has waited without a review or comment
- Flag anything waiting more than five days, and separately anything past two weeks
Done when Every stale pull request is identified with its wait time and repository.
-
2
Telegram - post the stale PR digest
telegram.org
WebRun opens Telegram to post the stale PR digest. - Post the daily digest to the team's Telegram group
- List each pull request waiting more than five days with its title and repository
- Include a link to each pull request
Done when The team has today's stale pull request digest in Telegram.
-
3
Twilio - text for the most overdue ones
twilio.com
WebRun opens Twilio to text for the most overdue ones. - Send a text to the repository maintainer for any pull request waiting more than two weeks
- Include the pull request title and repository
- Keep the message to one line
Done when The maintainer has been texted about every pull request waiting more than two weeks.
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 WebRun review or merge the pull request itself?
No. It only tracks how long a pull request has waited and notifies people. Reviewing and merging code stays entirely with your maintainers.
Why text only after two weeks?
A few days waiting for review is normal. Two weeks usually means it has been forgotten, so that is the point where it gets a direct text instead of just appearing in the daily digest.
Does it cover contributions from outside contributors too?
Yes. It checks every open pull request regardless of who opened it, which is useful for projects that get community contributions.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.