New deployment target Edit deployment target

Back to System settings
Callback URL pattern

Asynchronous strategies (e.g. WEBHOOK) must call back to the bot on this URL when the preview environment is ready. The {runId} and {secret} placeholders are filled in per request and embedded in the outbound webhook payload as callbackUrl.

Set the ai-git-bot.public-base-url property (e.g. https://bot.acme.io) so the bot can hand out a fully-qualified URL.
Unique identifier shown in the bot form dropdown.
Optional. Required by STATIC; informational for WEBHOOK. Placeholders: {prNumber}, {sha}, {branch}.
Maximum time the orchestrator waits for the strategy / callback.
WEBHOOK: { "webhookUrl": "<url>", "sharedSecret": "<hex>", "headers": { ... } }.
STATIC: { "healthcheckPath": "/healthz", "expectedStatus": 200, "intervalSeconds": 5, "extraHeaders": { ... } }.
MCP (experimental): { "mcpConfigurationId": <id>, "deployTool": "<qualified-name>", "statusTool": "<qualified-name>", "teardownTool": "<qualified-name>", "argsTemplate": { "branch": "{branch}", "sha": "{sha}" } }. All tool names must be whitelisted on the referenced MCP configuration — the save is rejected otherwise.
CI_ACTION: { "workflowRef": "preview.yml", "refTemplate": "refs/heads/{branch}", "previewUrlOutput": "preview_url", "pollIntervalSeconds": 15, "inputs": { "callbackUrl": "{callbackUrl}" } }. workflowRef is the workflow file (GitHub / Gitea Actions), the pipeline trigger token (GitLab CI) or the custom pipeline pattern (Bitbucket Pipelines). refTemplate must resolve to a branch or tag that already exists on the remote (default: refs/heads/{branch}) — Gitea, GitLab and Bitbucket reject pull-request refs such as refs/pull/N/head at dispatch time. GitHub Actions additionally supports refs/pull/{prNumber}/head (needed for fork PRs). See doc/PR_WORKFLOWS_CI_ACTIONS.md for one recipe per provider.
See doc/PR_WORKFLOWS.md → Deployment targets for the full schema.
Cancel