Skip to content

No PR check that stops invalid package version strings being released to trixie #35

Description

Expected: if I file a PR against qli/debian/trixie that has a version string like 1.877.5-0qli2 instead of the expected 1.877.5-0qli2~bpo13+1 then a PR check should fail.

Related to #18 but I think the PR check should exist regardless of that.

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