Copilot Agent Jira integration, Branch/PR naming issues

[michael-proctor]

Select Topic Area

Question

Copilot Feature Area

Copilot Coding Agent

Body

We are trialling using Github Copilot integration with Jira. The issue I have is that we have branch protections on with a regex pattern enforcing tickets follow "feature/(jira-id)-(title)" or "bugfix/(jira-id)-(title)" (if the type is Bug or Defect).

I have placed a custom instruction at Organization level but that doesn't seem to be used when the job runner starts the agent.

Copilot was unable to create a job for due to repository rules: job builder encountered known error and finalized job: job cannot be created due to repository rules violation: ["Branch name restrictions apply (must match regex ***) due to repository rules"]

When assigning the ticket to Copilot, how can we get it to follow the instruction? Within the chat window I have instructed it to use a branch, but the job runner seems to run first to create the branch for the agent to work out of then will pass the instruction to the agent which is too late.

[michael-proctor]

Someone asked something similar but not around the actual assigning of tasks and creating the job https://github.com/orgs/community/discussions/181529

[yesalphahere]

Copilot Coding Agent + Branch Protection Rules (Jira Integration)

---

What's Happening

The Copilot Coding Agent creates its branch before it reads any custom instructions. So by the time your org-level instruction is passed to the agent, the branch name violation has already occurred and the job is dead.

Agent triggered → Branch created (wrong name) → Rules violated → Job fails
                        ↑
              Your instruction arrives here (too late)

---

Why Org-Level Instructions Don't Help Here

Org-level custom instructions are passed to the chat agent, not the job runner. The job runner that spins up the Copilot workspace branch is a separate process that doesn't read those instructions before acting.

---

Current Workarounds

Option 1 — Pre-create the branch manually (most reliable right now)

Create the correctly named branch yourself before assigning to Copilot:

bash

git checkout -b feature/PROJ-123-my-feature-title
git push origin feature/PROJ-123-my-feature-title
```

Then assign the Jira ticket to Copilot — it will pick up the existing branch instead of creating one.

---

**Option 2 — Add a Branch Ruleset Exception for Copilot**

In GitHub → Repo Settings → Rules → Rulesets, add a bypass exception:
```
Bypass list → Add bypass → Copilot (app)

This lets the Copilot runner create its branch freely, then you can rename or enforce via PR title instead.

---

Option 3 — Relax the Regex Temporarily During Trial

Since you're in a trial phase, consider switching branch protection to enforce naming at the PR level via a GitHub Action rather than at branch creation:

yaml

on:
  pull_request:
    types: [opened, edited]

jobs:
  check-branch:
    runs-on: ubuntu-latest
    steps:
      - name: Validate branch name
        run: |
          BRANCH="${{ github.head_ref }}"
          if ! echo "$BRANCH" | grep -qE '^(feature|bugfix)/[A-Z]+-[0-9]+-[a-z0-9-]+$'; then
            echo "Branch name does not follow naming convention"
            exit 1
          fi

This moves enforcement to PR time — where Copilot's instructions can influence the process.

---

What GitHub Needs to Fix

This is a known gap. The job runner needs to:

1. Read org/repo custom instructions before branch creation
2. Support a copilot-branch-template config in .github/copilot-instructions.md

Worth raising directly via the feedback button in Copilot or the GitHub Community forum to push priority on this.

---

Recommended Approach for Your Trial

Step | Action -- | -- Short term | Pre-create branches before assigning to Copilot Medium term | Add Copilot as a bypass actor in your ruleset Long term | Move naming enforcement to PR-level GitHub Action

The core issue is a product gap, not a misconfiguration on your end. Pre-creating the branch is the cleanest workaround until GitHub adds pre-branch instruction support to the job runner.

Copilot Coding Agent + Branch Protection Rules (Jira Integration)

What's Happening
The Copilot Coding Agent creates its branch before it reads any custom instructions. So by the time your org-level instruction is passed to the agent, the branch name violation has already occurred and the job is dead.
Agent triggered → Branch created (wrong name) → Rules violated → Job fails
↑
Your instruction arrives here (too late)

Why Org-Level Instructions Don't Help Here
Org-level custom instructions are passed to the chat agent, not the job runner. The job runner that spins up the Copilot workspace branch is a separate process that doesn't read those instructions before acting.

Current Workarounds
Option 1 — Pre-create the branch manually (most reliable right now)
Create the correctly named branch yourself before assigning to Copilot:
bashgit checkout -b feature/PROJ-123-my-feature-title
git push origin feature/PROJ-123-my-feature-title

Then assign the Jira ticket to Copilot — it will pick up the existing branch instead of creating one.

---

**Option 2 — Add a Branch Ruleset Exception for Copilot**

In GitHub → Repo Settings → Rules → Rulesets, add a bypass exception:

Bypass list → Add bypass → Copilot (app)
This lets the Copilot runner create its branch freely, then you can rename or enforce via PR title instead.

Option 3 — Relax the Regex Temporarily During Trial
Since you're in a trial phase, consider switching branch protection to enforce naming at the PR level via a GitHub Action rather than at branch creation:
yamlon:
pull_request:
types: [opened, edited]

jobs:
check-branch:
runs-on: ubuntu-latest
steps:
- name: Validate branch name
run: |
BRANCH="${{ github.head_ref }}"
if ! echo "$BRANCH" | grep -qE '^(feature|bugfix)/[A-Z]+-[0-9]+-[a-z0-9-]+$'; then
echo "Branch name does not follow naming convention"
exit 1
fi
This moves enforcement to PR time — where Copilot's instructions can influence the process.

What GitHub Needs to Fix
This is a known gap. The job runner needs to:

Read org/repo custom instructions before branch creation
Support a copilot-branch-template config in .github/copilot-instructions.md

Worth raising directly via the feedback button in Copilot or the GitHub Community forum to push priority on this.

Recommended Approach for Your Trial
StepActionShort termPre-create branches before assigning to CopilotMedium termAdd Copilot as a bypass actor in your rulesetLong termMove naming enforcement to PR-level GitHub Action

The core issue is a product gap, not a misconfiguration on your end. Pre-creating the branch is the cleanest workaround until GitHub adds pre-branch instruction support to the job runner.