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:- Commits changes to Git with structured messages
- Creates branches following naming conventions
- Opens pull requests with metadata and reviewers
- Sends notifications via Slack, email, or webhooks
Delivery Specification
Git Modes
AgentGate supports three Git operation modes:- Local
- Push
- GitHub PR
Commit locally onlyChanges are committed but not pushed. Use for local development or when you want manual control over pushing.Workflow:
- Agent completes work
- Changes committed to local branch
- No remote operations
- 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:Pull Request Configuration
Configure pull request creation for thegithub-pr mode:
PR Spec Options
Auto-Merge Configuration
Enable automatic merging after checks pass:Notifications
Send notifications when tasks complete or fail:Notification Types
- Slack
- Email
- Webhook
Send to Slack channelOptions:
Template Variables
Available in notification templates:Complete Examples
Minimal Delivery
Standard PR Workflow
Full-Featured Delivery
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 fixesfeat/for featuresrefactor/for refactoringdocs/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
Push fails with authentication error
Push fails with authentication error
Ensure GitHub token has push permissions:
PR creation fails
PR creation fails
Check repository permissions:
- Token needs
reposcope for private repos - Token needs
public_repofor public repos
Slack notification fails
Slack notification fails
Verify webhook URL is correct:
Auto-merge not working
Auto-merge not working
Check repository settings:
- Branch protection rules must be enabled
- “Allow auto-merge” must be checked in repo settings
- All required checks must be passing
Related
TaskSpec
Configure delivery within TaskSpec
Execution
Execution environment configuration
Gates
Verification before delivery
GitHub Integration
Set up GitHub integration