Skip to content

Decouple CI behavior from output #57

@theseion

Description

@theseion

While the output is responsible for printing (see #56), in case of GitHub we currently also specifically use os.Exit(1). Strictly speaking, output and behavior for a target should be separated into different objects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions