Release Process — Develop → Main · Version 1.0 · 2026

From your branch
to Production.

Every change to a citizen application follows the same path: your branch → the develop branch → the Dev site → a date agreed with AI App Review → CAB approval → the main branch → Production. This page walks through each step and tells you exactly what to ask Claude.

2Permanent branches
2Sites: Dev and Production
0Times you touch main

First, what is a branch?

Your app’s code lives in GitHub. A branch is a named copy of that code. Working in a branch lets you make changes without touching what everyone else is using.

There are three branches you need to know about — and you only ever work in the first two.

your-branch

Your branch. A temporary copy Claude creates for one change. It is copied from the develop branch and merged back into the develop branch when you’re done.

develop

The develop branch. The shared copy that runs the Dev site. Every change is merged here first so it can be tested live.

main

The main branch. The copy that runs the Production site. Only the AI App Review group updates it, at a CAB-approved time.

When you start a change, Claude makes a new branch for you that is copied from the develop branch. You work in that branch, then ask to have it merged back into the develop branch. That’s the whole idea.

Two copies of your app

Each branch runs its own copy of the app. Dev is the testing site where changes show up first. Production is the real site your users rely on.

SiteRuns fromAddressWhat it’s for
Dev The develop branch {app-name}-ui-dev.azurewebsites.net Test your changes here before anyone else sees them. Updates automatically a few minutes after a merge into the develop branch.
Production The main branch {app-name}-ui.azurewebsites.net The live site. Updates automatically a few minutes after the AI App Review group merges into the main branch at the CAB-approved time.
ℹ️
Merging is deploying. There is no separate “deploy” button. Merging into the develop branch updates the Dev site; merging into the main branch updates Production. Treat both accordingly.

Eleven steps, two parts

Part 1 gets your change onto the Dev site so you can test it. Part 2 gets it approved and released to Production. Where a step is yours, there’s a “Tell Claude” prompt you can use word-for-word.

Part 1

Make the change and test it on Dev

Everything here happens in your branch and the develop branch. Nothing touches Production.

  1. 1
    Create your branch from the develop branch You + Claude

    Your branch is your own workspace for one change. It must be copied from the develop branch, not the main branch.

    Tell ClaudePull the latest develop branch and create a new branch off of the develop branch for [describe your change].
  2. 2
    Make your changes in your branch You + Claude

    Work with Claude as usual. Test your changes at http://localhost:5173. When they work, have Claude save and push your branch.

    Tell ClaudeCommit these changes with a clear message and push my branch.
  3. 3
    Open a Pull Request into the develop branch You + Claude

    A Pull Request (PR) asks the AI App Review group to review your branch and allow it into the develop branch. It must point at the develop branch. Include a short test summary.

    Tell ClaudeOpen a pull request from my branch into the develop branch. Summarize what changed and how I tested it.
  4. 4
    AI App Review approves, then you merge AI App Review You + Claude

    The review group looks over the PR and may ask for tweaks. Once they approve it, the merge is up to you — merge whenever you’re ready for the change to go to the Dev site.

    Tell Claude (after approval)My pull request into the develop branch has been approved — merge it.
  5. 5
    Dev updates itself Automatic

    Within a few minutes of the merge, your change is live on the Dev site. No action needed.

  6. 6
    Test your changes on the Dev site You

    Open the Dev site and test your changes the way a real user would. Something off? Go back to step 1 and create a new branch to fix it.

▼   Dev testing passed — time to schedule it with AI App Review   ▼

Part 2

Release to Production

This is the only part of the process that touches the main branch, and the AI App Review group performs it.

  1. 7
    Agree a release date with AI App Review You AI App Review

    Message the AI App Review group on Microsoft Teams before you go anywhere near a CAB ticket. Tell them which app, what’s shipping, and when you’d like it released. They’ll confirm a date and time someone in the group can staff. That agreed time is what goes on the ticket in the next step.

    🚫
    Do not file a CAB ticket until AI App Review has confirmed the date. The group performs the merge, so the time on the ticket has to be one they agreed to.
  2. 8
    Get CAB approval Change Management

    CAB (the Change Advisory Board) approves what goes to Production and when. Submit a Change Management ticket with a short description of what’s shipping, the date and time agreed in step 7, and the AI App Review group named as the team performing the change. Nothing moves to Production without this.

  3. 9
    AI App Review opens a PR from the develop branch into the main branch AI App Review

    Only the AI App Review group can do this. The PR carries everything already tested on Dev. Send the group your CAB ticket number once it’s approved and they’ll set it up.

  4. 10
    AI App Review merges into the main branch at the approved time AI App Review

    Merging into the main branch is what starts the Production update, so the review group performs it exactly at the time CAB approved — not before.

  5. 11
    Production updates itself Automatic

    A few minutes after the merge, open the Production site and test your changes there.

🚫
Never branch from or open a PR into the main branch. Feature work always targets the develop branch. The develop → main PR is opened and merged by the AI App Review group only.

Words you’ll see

Claude and GitHub will use these terms. Here’s what they mean in this process.

Branch

A named copy of the code. Your branch is where you make one change without affecting anyone else.

develop branch

The shared branch that runs the Dev site. All changes are merged here first.

main branch

The branch that runs the Production site. Only the AI App Review group updates it, at CAB-approved times.

Commit / push

Saving your work in your branch and sending it to GitHub so others can see it.

Pull Request (PR)

A request to have your branch reviewed and merged into another branch.

Merge

Accepting a PR so the change becomes part of the target branch. Merging into the develop branch updates Dev; merging into the main branch updates Production.

AI App Review group

The reviewers who approve PRs and perform the develop → main merge. Reach them via Microsoft Teams.

CAB

Change Advisory Board — approves Production changes and their timing through a Change Management ticket. File only after AI App Review has confirmed the date.

Six things that keep this smooth

Always say “the develop branch”

When asking Claude to create a branch or open a PR, name the develop branch. If Claude suggests the main branch, correct it.

You never merge into main

The AI App Review group does that, and only at the CAB-approved time.

Agree a date before asking CAB

CAB approves a time. AI App Review has to be free at that time to perform the merge. Confirm the date with them on Teams first, then file the ticket — and only after you’ve tested on Dev.

Merging into develop is your call — after approval

Wait for the AI App Review group to approve the PR, then merge when you’re ready to test on Dev.

One change per branch

Keeps reviews quick and problems easy to trace.

Not sure? Ask before opening a PR

Everything in your own branch is easy to undo. Reach the AI App Review group on Microsoft Teams.

Questions about the release process?

Reach out to the AI App Review group via Microsoft Teams, or contact the IT service desk for Change Management questions.