PR Gate · Configuration Wizard

Jira

Merge Gate

Branch Rules

Reviewers

Generate

Jira connection

Tell PR Gate where your Jira site is and which project keys to look for in PR titles and branch names.

Jira site URL

Project keys — type a key and press Enter or comma

e.g. PROJ, PLAT, INF — one per project you want PR Gate to recognise

Require ticket key in PR title?

Enforce in title

PRs without a key like ZA-123 in the title will be blocked

Merge gate

Choose which Jira statuses a ticket must be in before its PR can merge. PRs linked to a ticket outside these statuses will be blocked.

Allowed statuses for merge

Auto-transition on PR open — optional

Auto-transition on PR merge — optional

Branch naming

Optionally enforce a naming convention on branches. Use {ticket} as a placeholder for the Jira key pattern.

Enable branch naming check?

Check branch names

PRs from branches that don't match the pattern will be flagged

Pattern preset

Pattern — regex, {ticket} expands to your project key(s)

Enforcement

Reviewer policy

Control what happens when a PR has no reviewer assigned.

Reviewer required

Auto-labelling from Jira

Label from issue type

Bug → bug, Story → enhancement, Task → task

Label from priority

Highest/High → priority:high, Medium → priority:medium, etc.

Your config files

Commit both files to your repository root. Add the three GitHub secrets listed below, then set PR Gate as a required status check in your branch protection rules.

.pr-gate.yml

.github/workflows/pr-gate.yml

GitHub secrets to add

JIRA_BASE_URL your Jira site URL

JIRA_EMAIL the email address for your Jira API token

JIRA_API_TOKEN generate at id.atlassian.com → Security → API tokens