Skip to content

Concurrency key unnecessarily blocks across distribution channels #324

@EricCrosson

Description

@EricCrosson

For example, I have two release workflows trying to run independently, one on the main release channel and one on beta. The second workflow is queued behind the first due to the present concurrency rules. Is this a bug? Noodle on it. Gut instinct is that it is.

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