Skip to content

Propagate custom env vars to the API checker soundness check #205

Description

@czechboy0

Propagate custom env vars to the API checker soundness check:

This is needed as we use env vars to enable all traits in most CI pipelines for packages that have any non-default package traits.

Setting this env on the workflow that calls this one doesn't seem to do the job, maybe they need to be propagated explicitly? That's what we do elsewhere: https://github.com/apple/swift-nio/blob/888f4affd6cc7629adace9492c95504dd5201ae1/.github/workflows/benchmarks.yml#L168

cc @rnro

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