Digger home pagelight logodark logo
  • diggerhq/digger
  • diggerhq/digger
  • Documentation
  • Slack
  • Blog
  • Introduction
    • About Digger
    • How it works
    • Pricing
    • FAQ
    • Feedback
    Getting Started
    • Github Actions + AWS
    • Github Actions + GCP
    Features
    • Plan preview
    • CommentOps
    • Dashboard
    • OPA policies
    • Concurrency
    • PR-level locks
    • Plan Persistence
    • RBAC
    How To
    • Apply on Merge
    • Auto-merge
    • Backendless mode
    • Commenting strategies
    • Custom commands
    • Destroy via manual workflow
    • Disable auto-checkout
    • Drift Detection
    • Generate projects
    • Include / exclude patterns
    • Multiple AWS accounts
    • Policy overrides
    • Project Level Roles for AWS
    • Segregate cloud accounts
    • Trigger workflow directly
    • Using Checkov
    • Using Infracost
    • Using OPA (Conftest)
    • Using Terragrunt
    • Specifying version
    Self-host Digger
    • Auth methods
    • Deploy as docker image
    • Deploy using docker-compose
    • Deploy as a binary
    Reference
    • digger.yml
    • Action inputs
    Digger Enterprise
    • Setting up Digger EE
    Digger API
    • RBAC via OPA guide
    AWS-specific
    • Setting up DynamoDB Access for locks
    • Setting up separate mgmt account
    • Authenticating with OIDC on AWS
    GCP-specific
    • Setting up GCP + GH Actions
    • Federated OIDC access
    • Store plans in a Bucket
    Azure-specific
    • Setting up Azure + GH Actions
    • Azure devops locking connection methods
    Troubleshooting Errors
    • Importing existing resources
    How To

    Auto-merge

    You can set auto_merge: true option to automatically merge the PR when all checks pass (including successful apply). Note that it’s a top-level setting, not project level:

    projects:
    - name: development
      dir: dev
    - name: production
      dir: prod
    auto_merge: true
    
    Apply on MergeBackendless mode
    slacklinkedin
    Powered by Mintlify