Skip to content

GitHub actions enforcing documentation for attack paths #6

@Skybound1

Description

@Skybound1

Workflows should enforce we have documentation for each attack path defined.

Should be a simple check that iterates over attack path names and ensures a relevant markdown file is present in /docs/

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