Skip to content

Keep single pipeline for PR check and release #701

@vifactor

Description

@vifactor

The release and pull request (PR) pipelines are maintained as two separate setups. As a result, the regular CI process does not validate the functionality of the release pipeline. This disconnect means that issues within the release pipeline often go unnoticed until the actual release occurs—typically only twice a year—which is far too late for timely resolution.

This might help avoiding issues like this: #698

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions