Automated Gitee Issue Triage Queue
Every morning, WebRun signs in to Gitee, collects the issues opened overnight across your repositories, groups them by repository with anything urgent called out, drafts a suggested label, milestone, and assignee for each in Notion, and logs the triage queue in Airtable.
How do I triage new Gitee issues every morning?
WebRun signs in to Gitee every morning and collects the issues opened overnight across your repositories, grouping them by repository with crashes and security reports called out. It drafts a suggested label, milestone, and assignee for each in Notion and logs the queue in Airtable, so triage takes minutes instead of a week.
- Overnight issues are labelled and owned the next morning
- Crash and security reports are surfaced above routine requests
- Likely duplicates are flagged before two people work them
Built for open source maintainers · engineering leads · developer teams · QA 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
gitee.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Gitee - collect the overnight issues
gitee.com
WebRun opens Gitee to collect the overnight issues. - Sign in to Gitee and open the issue list for each repository you maintain
- Collect issues opened since the last run that carry no label and no assignee
- Capture the title, the reporter, the repository, and the opening comment
- Group by repository and mark anything describing a crash, data loss, or a security concern as urgent
- Note duplicates of an issue already open so they are not triaged twice
Done when Every unlabelled overnight issue is captured and grouped by repository.
-
2
Notion - draft a label and owner for each
notion.so
WebRun opens Notion to draft a label and owner for each issue. - Add each issue to your triage page with a one line summary in plain language
- Suggest a label, a milestone, and an assignee based on the repository and the text
- Put the urgent items at the top with the reason they were marked urgent
- Leave every suggestion as a draft. WebRun does not label, assign, or comment on the issue in Gitee
Done when Every new issue has a suggested label, milestone, and owner waiting in Notion.
-
3
Airtable - log the triage queue
airtable.com
WebRun opens Airtable to log the triage queue. - Log each issue with its repository, reporter, date, and suggested label
- Track how many issues arrive per repository each day
- Flag repositories where the untriaged backlog is growing week over week
Done when Today's triage queue is recorded in Airtable.
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 comment on issues or assign people in Gitee?
No. Every label, milestone, and assignee is a suggestion written into Notion. WebRun never comments on a public issue, applies a label, closes anything, or notifies a reporter.
How does it decide what is urgent?
By what the issue describes. Reports of a crash, data loss, or a security concern are marked urgent and put at the top of the queue, with the reason stated so you can disagree quickly.
Does it catch duplicate issues?
Yes. It checks new arrivals against issues already open in the same repository and notes likely duplicates, so the same problem is not triaged and assigned twice.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.