Evally
Start free
Engineering

PR labeler

Label pull requests by type and area, and flag what belongs in the changelog.

Reads a PR's title, description and changed files, labels its type and area, and says whether users will notice and whether it belongs in the changelog. Size is measured as scope, not lines.

Use this judgeCustomize it

Try it live

Real calls to Jev. Pick an example or paste your own.

Examples
31
0
30
No verdict yet

Pick an example or paste your own input, then run it.

Under the hood

Every question and rule, in the open. Fork it to change any of them.

What it asks

Reads title, description and files, then asks 4 questions in one call.

  1. Q1TypePick one

    What kind of pull request is this?

    FeatureBug fixRefactorDocsTestsDependenciesCI/buildSecurityOther
  2. Q2AreaPick one

    Which part of the codebase does it mainly change?

    FrontendBackendDatabaseInfrastructureMobileDocsSeveral areasOther
  3. Q3User-facingYes / no

    Would users notice this change?

  4. Q4Changelog-worthyYes / no

    Should this change be mentioned in the changelog?

How it decides

Rules run in code, top to bottom. The first one that matches gives the verdict.

  1. 1
    Otherwisethe answer to “Type”
  2. ·
    DefaultFeature

Call it from your code

Every template runs as-is with an API key, no setup: POST /api/v1/judges/pr-labeler/run.

curl -X POST https://tryevally.com/api/v1/judges/pr-labeler/run \  -H "Authorization: Bearer $EVALLY_API_KEY" \  -H "Content-Type: application/json" \  -d '{  "input": {    "title": "Bump next from 16.3.4 to 16.3.5",    "files": "package.json\npackage-lock.json"  }}'

Seen in the wild

Community builds on Jev that use this pattern. Not affiliated with Evally.

More in Engineering