Skip to content

Feature Request: Abstract the acquisition of a scratch org behind configuration. #2112

@codefriar

Description

@codefriar

As a Metecho user with a moderately complex org, it can take ~90 minutes for a scratch org to be spun up. Our internal solution to this at Chief is to use scratch org pooling. I would love to be able to configure how Metecho acquires a scratch org, so that I can direct Metecho to 'adopt' a scratch org, rather than create a net new one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions