Skip to content

[Feature request] First formality check and then something else #55

@BKPepe

Description

@BKPepe

In the packages repository, whenever a PR is opened, the workflow runs the formality check and, regardless of the result, it also starts heavy jobs like multi-arch test builds. If the formality check fails, those resource-intensive jobs still run unnecessarily. Later, when the contributor fixes the formality issue, the same heavy jobs are triggered again.

This behavior causes excessive CI/CD resource usage and increases the queue time for other jobs. So, run the formality check first, and only if it passes, trigger the heavy jobs (multi-arch builds and similar). This would reduce wasted resources and improve overall CI efficiency.


For the packages repository, I propose something like this: openwrt/packages#27592

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions