All templates

Automated Gitea Pull Request Review Scheduling

Every morning, WebRun opens Gitea Cloud, reviews open pull requests across your repositories, books a review slot on the reviewer's Google Calendar for anything waiting more than four days, and posts the full list to Microsoft Teams so nothing sits waiting indefinitely.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Gitea Cloud review open pull requests
2 Google Calendar schedule a review slot
3 Microsoft Teams post the review digest
In short

How do I stop Gitea pull requests from waiting too long for review?

WebRun reviews open Gitea Cloud pull requests every morning, and for anything waiting more than four days, books a review slot directly on the reviewer's Google Calendar. It also posts the full review queue to Microsoft Teams grouped by reviewer, so pull requests get both protected time to be reviewed and visibility across the whole team.

  • Stale pull requests get a protected calendar slot instead of an easily ignored ping
  • The whole team can see the review queue in Teams every morning
  • Reviews get scheduled proactively instead of waiting for someone to complain

Built for Engineering teams · self-hosted Git users · engineering managers · small development teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens gitea.com/user/login in a real browser with your saved login - no setup, no API keys.

  2. 1
    Gitea Cloud - review open pull requests
    gitea.com
    WebRun in Gitea Cloud: review open pull requests
    WebRun opens Gitea Cloud to review open pull requests.
    • Open Gitea and review open pull requests across repositories
    • Check how many days each has waited without a review
    • Flag anything waiting more than four days and note the assigned reviewer

    Done when Every pull request waiting more than four days is identified with its reviewer.

  3. 2
    Google Calendar - schedule a review slot
    calendar.google.com
    WebRun in Google Calendar: schedule a review slot
    WebRun opens Google Calendar to schedule a review slot.
    • Open the assigned reviewer's Google Calendar
    • Book a 20 minute review slot within the next two business days
    • Include the pull request title and link in the event notes

    Done when A review slot is booked for every pull request waiting more than four days.

  4. 3
    Microsoft Teams - post the review digest
    microsoft.com
    WebRun in Microsoft Teams: post the review digest
    WebRun opens Microsoft Teams to post the review digest.
    • Post the full list of open pull requests to the engineering Microsoft Teams channel
    • Group them by reviewer and note how long each has waited
    • Link directly to each pull request

    Done when The team has today's pull request review digest in Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
gitea.com/user/login
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Review chase list · Microsoft Teams
OutputWhat each run produces - A booked review slot for pull requests waiting more than four days and a daily Teams digest of the full review queue.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will WebRun review or merge the pull request itself?

No. It only tracks how long a pull request has waited and books time for a human reviewer. Reviewing and merging code stays entirely with your team.

How is the reviewer chosen for the calendar booking?

From whoever is already assigned as reviewer on the pull request in Gitea, so the booking goes to the right person automatically.

What if the review already happened by the time of the slot?

The booked slot is just protected time. If the review is already done, the reviewer can simply skip it.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.