Skip to content

Enforce approval before publishing #28

@annda

Description

@annda

Feature Description

Currently it is possible to skip the approval step and directly publish a draft. In many cases this is not desirable. In the publish plugin this is handled by a separate option: required number of publishers.

In structpublish I suggest introducing an option that will disable skipping stages, even if the user has appropriate rights. Alternatively, we could make the no-skip policy default and have an additional option to enable skipping.

PR #27 takes a step in this direction in 2ef4cda, but it is very specific to the publish action. I would like to see a more general approach. In the future the chain of publishing steps might look different, but the principle of no-skipping should hold.

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