PR Naming Enforcement

Ensure consistent PR naming conventions across your team.

Overview

PR naming enforcement helps maintain consistent conventions across your team. Jasper can validate PR titles against configurable patterns and enforce compliance through GitHub Checks.

Setting Up PR Naming Rules

Configure PR Naming

Set up your PR naming rules in the dedicated settings page.

Open PR Naming Settings
  1. Navigate to Settings → PR Naming
  2. Define your naming pattern (e.g., [TICKET-ID] type: description)
  3. Configure allowed types (feat, fix, docs, etc.)
  4. Set enforcement level

Enforcement Levels

Level Behavior
Warn Show warning in review but allow merge
Block Fail the GitHub Check, prevent merge until fixed
Auto-fix Suggest corrected titles automatically

Example Patterns

Pattern Valid Example
[CU-ID] type: description [CU-abc123] feat: add user login
type(scope): description feat(auth): implement SSO
PROJ-123: description PROJ-456: fix navigation bug

Common Types

Recommended conventional commit types:

  • feat - A new feature
  • fix - A bug fix
  • docs - Documentation changes
  • style - Formatting, missing semicolons, etc.
  • refactor - Code restructuring without feature changes
  • test - Adding or updating tests
  • chore - Maintenance tasks

GitHub Check Integration

When enforcement is enabled, Jasper creates a GitHub Check that:

  • Runs automatically when PRs are opened or updated
  • Shows pass/fail status in the PR checks section
  • Provides detailed feedback on naming issues
  • Can block merging if configured to "Block" level

Next Steps

Status Sync Ticket Templates