Skip to content

Canary build workflow clones HEAD not the triggering commit #11724

@kenodegard

Description

@kenodegard

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

When canary builds are run, they clone and build from main's HEAD, not the commit triggering the build. This means that if we merge multiple PRs in quick succession, then all of those canary builds will generate the same canary builds, not unique builds per commit.

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogissue has been triaged but has not been earmarked for any upcoming releaseseverity::4low; functionality is inconvenientsource::anacondacreated by members of Anaconda, Inc.stale::recovered[bot] recovered after being marked as staletype::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions