Skip to content

Adding extension to release created in the tool #10

@ghost

Description

When you work with an existing Process then that process might already have extensions, and they should be kept (as you can't remove an extension half way through an contracting process)

The tool should add existing extensions by default when addemptyrelease (think it already does)?

But what if you want to start using another extension?

Either

  • the tool could have an option for this to make it easier
  • we should document how to do this

Currently, after running addemptyrelease you would just edit the package.json (I think)

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