Reusable GitHub Actions workflow that creates a Support Platform change when a PR contains a change-request block.

Copy .github/workflows/caller-template.yml into your gitops repo and rename it:

jobs:
  create-change:
    uses: intility/change-manager-workflow/.github/workflows/create-change.yml@main
    secrets: inherit
    with:
      pr-body:   ${{ github.event.pull_request.body }}
      pr-number: ${{ github.event.pull_request.number }}
      pr-title:  ${{ github.event.pull_request.title }}
      pr-url:    ${{ github.event.pull_request.html_url }}
      pr-author: ${{ github.event.pull_request.user.login }}
      repo:      ${{ github.repository }}

Add a change-request block to the PR description. Remove it entirely for PRs that are not tracked changes.

```change-request
title: "Short title (4–60 chars)"

# Owner — pick one, or omit to default to the PR author
owner_upn: "[email protected]"
# owner_guid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

started_on: "2026-04-20T22:00:00Z"
ended_on:   "2026-04-20T23:00:00Z"
impacts_all: false

# Optional
# description: "..."
# is_internal: true
# assets:
#   - "14ea6945-a8ec-4cd9-8ae8-a3d8c0778a2c"  # Intility Developer Platform
# tickets:
#   reference_numbers: [12345]
# hyperlinks:
#   - name: "Runbook"
#     url: "https://wiki.example.com/runbook"
```

On PR open or edit the workflow creates the change and posts a comment with the change ID and a direct link to it in Support Platform.

Set once at org level — calling repos need nothing:

The app registration needs:

• Support Platform API (api://6563f833-21a5-4b8a-90ee-37a36cf8f667): Processes.Modify — Application permission, admin consent required
• The service identity must be registered in the Support Platform database (used to resolve UPN → GUID via the users query)