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
    Digger Enterprise
    • Setting up Digger EE
    • Drift Detection
    • RBAC
    • OPA Policies
    • Multi Tenant Github Connections
    • Gitlab Pipelines
    • Buildkite CI backend
    • FIPS 140 standard
    • AI Summaries
    Features
    • Plan preview
    • CommentOps
    • Policies (OPA)
    • Concurrency
    • PR-level locks
    • Plan Persistence
    • Private Runners
    How To
    • Managing state
    • Specify terraform version
    • Apply on Merge
    • Apply Requirements
    • Auto-merge
    • Backendless mode
    • Commenting strategies
    • Custom commands
    • Destroy via manual workflow
    • Draft PRs
    • Disable auto-checkout
    • Disable telemetry
    • Generate projects
    • Group plans by source module
    • Include / exclude patterns
    • Masking sensitive values
    • Multiple AWS accounts
    • Policy overrides
    • Project Level Roles for AWS
    • Segregate cloud accounts
    • Store plans in a Bucket
    • Trigger workflow directly
    • Using Checkov
    • Using Infracost
    • Inline policies (conftest)
    • Using Terragrunt
    • Specifying version
    Self-host Digger
    • Auth methods
    • Deploy as docker image
    • Deploy using docker-compose
    • Deploy as a binary
    • Digger Helm Chart
    • Self Host on Azure
    Reference
    • digger.yml
    • Action inputs
    • Orchestrator API
    • handling terraform.lock file
    • Securing digger
    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
    • Using GCP bucket for locks
    Azure-specific
    • Setting up Azure + GH Actions
    • Azure devops locking connection methods
    Troubleshooting
    • Importing existing resources
    • Action Errors
    • PR Comment Issues
    How To

    Commenting strategies

    • The way digger comments plan previews on PRs can be configured based on the requirement of verbosity or summary. The value of the summary can be configured using the reporting-strategy parameter: https://github.com/diggerhq/digger/blob/develop/action.yml#L105

    • If you have many projects and would like to not pollute your pull requests with several plan comments for every you should chose comments per run or latest run reporting strategies which will shrink comments to a single comment per push

    • If you would like a more verbose output you should chose the multiple comments strategy

    • More details about the reporting strategy can be seen in the reporter interface: https://github.com/diggerhq/digger/blob/5815775095d7380281c71c7c3aa63ca1b374365f/pkg/reporting/reporting.go#L12

    Was this page helpful?

    Suggest editsRaise issue
    Backendless modeCustom commands
    slacklinkedin
    Powered by Mintlify
    Assistant
    Responses are generated using AI and may contain mistakes.