Skip to content
Metatext Decide — typed decisions for your agents, with a probability on every answerGet early access
Metatext
Sign Up

JEV GitHub Labeler

Self-hosted Next.js API and GitHub Actions workflow that has Jev pick one label for each new issue or pull request.

Servicebeta
View on GitHub ↗

Overview

Jev GitHub Labeler is a self-hosted Next.js API that classifies GitHub issues and pull requests with Jev through Vercel AI Gateway. A GitHub Actions workflow sends the title, optional body and editable label criteria to the classify-issue or classify-pr endpoint, and the API returns one of the supplied labels, such as bug, enhancement, documentation, question, duplicate, good first issue, help wanted or invalid, which the workflow applies.

It is aimed at maintainers who want automatic first-pass labelling with label definitions they control. Deployment uses a one-click button and a shared LABELER_API_KEY secret between the deployment and the repository; the target repository stores the deployment URL as an Actions variable. Label names and descriptions are edited directly in the workflow script.

What the decision model decides

TypeQuestionAnswers
ChoiceWhich label best fits this issue or pull request?bug · enhancement · documentation · question · duplicate · good first issue · help wanted · invalid

How it works

  1. Deploy the API and set LABELER_API_KEY
  2. Add the workflow and variables to the target repository
  3. On a new issue or PR, send title, body and label criteria
  4. Apply the returned label

Strengths

  • Custom label definitions per repository
  • Runs inside existing GitHub Actions
  • Self-hosted

Caveats

  • Requires a Vercel AI Gateway key on the deployment
  • Always picks one label; no confidence handling described

Getting started

Deploy with the README's button, set LABELER_API_KEY, then add .github/workflows/classify-issues.yml with LABELER_URL and LABELER_API_KEY configured.

At a glance

Type
Service
Status
beta
Language
TypeScript
Runtime
Next.js API with GitHub Actions
Has code
yes

Use cases and integrations

How curated lists describe it

  • Automatically label GitHub issues and pull requests with Jev. Self-hosted Next.js API with GitHub Actions workflows and custom label support.

    hellogumbo/awesome-jev

Frequently asked questions

What does Jev decide?

Which of your labels fits each new issue or pull request.

Can I change the labels?

Yes, edit the names and descriptions in the workflow script.

Where does it run?

As your own Next.js deployment called from GitHub Actions.

Related projects

  • metis

    Small Python framework and GitHub Action for Jev-powered workflows, with issue triage and PR screening built as examples.

    ProjectbetaPython
  • Paca

    Self-hosted Jira alternative where AI agents join Scrum teams; Jev auto-assigns tasks, fills fields and routes workflow conditions.

    ServicebetaTypeScript
  • smart-labeler

    GitHub Action that applies a repository's existing labels to new issues and PRs, asking Jev one question per label group in one request.

    ProjectbetaTypeScript
  • agentrun

    Workflow DSL for existing agents that uses Jev for the steps that are decisions and calls an agent only when investigation is needed.

    LibrarybetaTypeScript
  • n8n-nodes-jev-classification

    n8n Jev Classification node that branches items by category with a Needs Review branch, plus parallel and batched requests.

    ProjectbetaTypeScript
  • jev-mail-classifier★ 21

    Config-driven IMAP inbox classifier with a terminal UI where Jev answers yes/no per category to tag, move, flag or notify.

    ProjectbetaPython