Skip to content

Release pull request checks #6

Description

@Maximilian-Nesslauer

The path for listings without a [releases] section, and the only path for content hosted anywhere the watcher does not watch.

The checks do not trust the submitted document: download the archive from its download.url, recompute the hash, the sizes and the install root, re-run the dependency merge against the authored file, and reject the submission when any stamped field disagrees with what the check computed.

Exactly one new file, whose path and version do not exist yet.

Ownership and auto-merge work exactly as in the listing flow, KSAModding/content-index#4.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:infraCI, workflows, automationarea:publishinglisting and release flows

    Type

    No type

    Projects

    Status
    Inbox

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions