Automated Bit Component Review Chase List
Every morning, WebRun opens Bit, reviews components with a pending change request or new version, flags any waiting on review for more than three days, creates a Trello card for tracking, and messages the component maintainer on WhatsApp so shared components do not stall the teams that depend on them.
How do I stop shared Bit components from stalling in review?
WebRun reviews your Bit component workspace every morning for change requests waiting more than three days, creates a Trello card for tracking, and messages the maintainer directly on WhatsApp. This keeps shared components from silently blocking the other teams that depend on them, since a stalled review gets both a visible card and a direct nudge.
- Stalled component reviews get a card and a ping within a day of going stale
- Maintainers are notified directly instead of relying on a mention getting seen
- Teams depending on shared components are not blocked for longer than needed
Built for Frontend platform teams · design system maintainers · component library owners · engineering 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
bit.dev/loginin a real browser with your saved login - no setup, no API keys. -
1
Bit - find stalled reviews
bit.dev
WebRun opens Bit to find stalled reviews. - Open Bit and review components with a pending change request or new version
- Check how long each has been waiting on review
- Flag any pending more than three days and note the maintainer
Done when Every component with a stalled review is identified with its wait time and maintainer.
-
2
Trello - create the tracking card
trello.com
WebRun opens Trello to create the tracking card. - Open the Component Reviews Trello board
- Create a card for each stalled component with its wait time and a link to Bit
- Place it in the Needs Review column
Done when A Trello card exists for every component review stalled more than three days.
-
3
WhatsApp - ping the maintainer
whatsapp.com
WebRun opens WhatsApp to ping the maintainer. - Message the component's maintainer on WhatsApp
- Include the component name, how long it has waited, and the Trello card link
- Ask them to review it or reassign the review
Done when The maintainer has been messaged about every stalled component review.
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 approve or merge the component change itself?
No. It only tracks how long a review has been waiting and notifies the maintainer. Approving or merging any change stays a human decision in Bit.
How is the maintainer chosen?
From the ownership already recorded against the component in Bit, so the ping goes to whoever is actually responsible for it.
What happens once the review is done?
The next morning's check sees the completed review and the card moves off the active chase list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.