GitHub Issue Triage
Automate GitHub issue triage with Nebula — label, prioritize, and assign new issues based on content to keep your backlog organized hands-free.
What you'll build
When new issues come in, Nebula reads each one, adds appropriate labels (bug, feature, docs), sets a priority, and assigns it to the right team member based on the area of code, so your backlog stays organized without anyone manually sorting through it.
What to say
Look at the open issues in our-org/our-repo that don't have labels. Read each one, add appropriate labels, and assign based on the area of code.
Found 3 unlabeled issues. Reading each one...
Triaged all 3 issues:
- #214 tagged bug/critical, assigned to @alex (backend)
- #215 tagged feature/medium, assigned to @maya (frontend)
- #216 tagged docs/low, assigned to @jordan (docs)
What happens
Nebula connects to GitHub and fetches unlabeled issues
Nebula asks your GitHub account for all open issues that haven't been labeled yet. It pulls the full title, body, and any existing metadata for each one.
Each issue is read and categorized
Nebula reads the title and description of each issue and determines what kind it is: a bug report, a feature request, a documentation gap, or a general question.
Labels and priority are assigned
Based on the category and severity described in the issue, Nebula applies the appropriate labels and sets a priority level. Here's an example of what that looks like across three issues:
Issue #214: "Clicking Save on the settings page throws a 500 error"
Labels: bug, priority: critical
Assigned to: @alex (backend)
Issue #215: "Add support for dark mode in the dashboard"
Labels: feature, priority: medium
Assigned to: @maya (frontend)
Issue #216: "README doesn't explain how to set up local environment"
Labels: docs, priority: low
Assigned to: @jordan (docs)
The right team member is suggested or assigned
Nebula looks at the area of code involved (backend, frontend, docs, infrastructure) and assigns the issue to whoever owns that area. If it can't determine ownership confidently, it flags the issue for manual assignment instead.
Make it automatic
When a new issue is created in our-org/our-repo, triage it automatically.
Creating event trigger: on new issue in our-org/our-repo. Task: read issue, categorize, apply labels, assign to team member.
Registered webhook for issues.opened events on our-org/our-repo.
Your event trigger is live. Whenever a new issue is opened, I'll read it, add the right labels (bug, feature, docs), set a priority, and assign it to the right person. You can pause or edit this from the Triggers page.
This sets up an event trigger that fires whenever a new issue is opened. Each issue gets labeled, prioritized, and assigned the moment it appears, no manual review needed.
Connect your integrations
This recipe uses GitHub. Connect your GitHub account from the Integrations page. Make sure the repositories you want to triage are accessible to the account you connect.
Related recipes
Development
Automate development workflows with Nebula recipes — GitHub issue triage, deployment alerts, code review digests, and custom API integrations.
Deployment Notifications
Automate deployment notifications with Nebula. Post summaries to Slack whenever your team ships — version numbers, changes, and who deployed.