What it does
The category descriptions live in a YAML file, so a team can change its policy without changing the classifier.
Integrations
Sort new GitHub issues into routine maintenance, technical investment or product work, and add the matching label.
Only you can see your notes.
Screenshot unavailable. Open the experiment ↗
The category descriptions live in a YAML file, so a team can change its policy without changing the classifier.
For a team that wants a clearer picture of incoming work, study the issue classifier and edit its category descriptions to match your team's definitions. Start with a dry run, which chooses a label without adding it to GitHub. It still sends issue text to paid Jev, so use suitable test messages.
Create the configured labels in GitHub before enabling automatic classification. It handles newly opened issues, not edits or old issues. Review the labels yourself: sending uncertain answers to a person is only proposed future work. No overall project license was found, so check permissions before reusing its code.