Skip to content

Decide Dependabot approval and automerge policy #222

Description

@jgeluk

The stale branch behind PR #151 contains unrelated workflows for automatic Dependabot approval and merge. The ontology fixes in that PR were already delivered elsewhere, leaving the automation proposal without its own issue or policy decision.

Decide which dependency classes may be auto-approved or auto-merged, required checks, version constraints, permissions, and failure behavior. Add workflow regression coverage first; do not silently merge dependency changes without an explicit policy.

Source candidate: PR #151, commit d541f08.

Related: #202, #213.

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildBuild and publish workflow, site generationdependenciesPull requests that update a dependency file

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions