Skip to content

Add codepush action? #3

@cball

Description

@cball

We can keep this as a separate action by default, but optionally have it called from the production release cycle for non-breaking releases (minor & patch).

If we're able to codepush, I think we should also be able to intelligently select the target. Assuming version 1.1.0:

  • A version bump to 1.1.1 could target 1.x.x
  • A version bump to 1.2.1 could target 1.x.x
  • A version bump to 2.0.0 would not codepush

Use the scripts we have locally in projects, and if possible leverage some logic from: https://github.com/manuelkch/fastlane-plugin-code_push

If it's not possible to properly automate, lets keep as a separate action with the prompts we use to simplify it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions