Skip to content

[new rule] create a new rule to deal with scope changes #70

Description

@BirgitBader

Context

We figured that we need a guideline on how to deal with scope changes. The existing rules focus too much on request/response bodies. The rule should belong in the compatibility section.

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