Skip to content

campaigns validate should require that changesetTemplate be defined #406

@evanweible-wf

Description

@evanweible-wf

Currently, a campaign.yaml spec can completely omit the changesetTemplate section and src campaigns validate will pass. As soon as you add the top-level changesetTemplate key, then the required fields within it are validated like so:

parsing campaign spec: 3 errors occurred:
        * changesetTemplate: title is required
        * changesetTemplate: branch is required
        * changesetTemplate: commit is required

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions