Skip to content

Automated package publishing #3

Description

@junhoyeo

When new code is pushed to main branch:

  • 💡 (Optional) Figure out scope of impacted modules
  • 💡 Automatically publish these modules to NPM registry
  • Maybe we can write another module for this feature, since we're going to manage multiple SDKs in the near future

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    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