Skip to main content

Delivery

Delivery configuration controls how AgentGate ships completed work. This includes Git operations, pull request creation, and notifications to stakeholders.

What Is Delivery

After an agent successfully completes a task (all gates pass), the delivery phase:
  1. Commits changes to Git with structured messages
  2. Creates branches following naming conventions
  3. Opens pull requests with metadata and reviewers
  4. Sends notifications via Slack, email, or webhooks

Delivery Specification

Git Modes

AgentGate supports three Git operation modes:
Commit locally onlyChanges are committed but not pushed. Use for local development or when you want manual control over pushing.
Workflow:
  1. Agent completes work
  2. Changes committed to local branch
  3. No remote operations
Best for:
  • Local development
  • Manual review before push
  • Testing and debugging

Git Configuration

Git Spec Options

Configuration Options

Branch Naming

Branches are named using the pattern: {branchPrefix}{task-slug}

Commit Messages

Commit messages can be customized using templates:
Available Variables:

Pull Request Configuration

Configure pull request creation for the github-pr mode:

PR Spec Options

Auto-Merge Configuration

Enable automatic merging after checks pass:
Auto-merge requires the repository to have branch protection rules enabled and the allow auto-merge setting turned on.

Notifications

Send notifications when tasks complete or fail:

Notification Types

Send to Slack channel
Options:

Template Variables

Available in notification templates:

Complete Examples

Minimal Delivery

Standard PR Workflow

Delivery Results

After delivery, AgentGate returns structured results:

Best Practices

1

Use Descriptive Branch Names

Use branch prefixes that indicate the type of change:
  • fix/ for bug fixes
  • feat/ for features
  • refactor/ for refactoring
  • docs/ for documentation
2

Add Meaningful Labels

Labels help with organization and filtering:
3

Assign Appropriate Reviewers

Match reviewers to the type of change:
4

Configure Failure Notifications

Always set up failure notifications for visibility:
5

Use Auto-Merge Carefully

Only enable auto-merge for well-tested, low-risk changes:

Troubleshooting

Ensure GitHub token has push permissions:
Check repository permissions:
  • Token needs repo scope for private repos
  • Token needs public_repo for public repos
Verify webhook URL is correct:
Check repository settings:
  1. Branch protection rules must be enabled
  2. “Allow auto-merge” must be checked in repo settings
  3. All required checks must be passing

TaskSpec

Configure delivery within TaskSpec

Execution

Execution environment configuration

Gates

Verification before delivery

GitHub Integration

Set up GitHub integration