Skip to content

undiverged branches #2073

@motatoes

Description

@motatoes

as mentioned in https://docs.digger.dev/ce/howto/apply-requirements#requiring-undiverged-branches-in-prs the default behavoiur of digger still comes with some risks if the requirement for undiverged branches is not checked in digger.yml

In order to protect users this should be the default behaviour to check for diverged branches unless users intend to turn it off. Proposal is to add a flag that is enabled by default to check for undiverged branches before any plan/apply commands. This would be similar to https://www.runatlantis.io/docs/command-requirements#undiverged

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions