Skip to content
This repository has been archived by the owner on Apr 17, 2024. It is now read-only.

Contribution

Jonas Büchel edited this page Oct 10, 2022 · 6 revisions

Branches setup

  • main: used for the regular public releases according to semantic releases.
  • next: used for next-releases, also accessible via npm. This releases are automatic created with every merged PR into next

How to contribute

Create a branch of next. Squash-merge your changes back to next via a pull request once you are done.

How to create and publish a release

  • Create a PR with a request to merge next into main.
  • Merge next into main by using "create a merge commit". ATTENTION: Make sure you don't use squash-merge, otherwise main and next will go off track. Use the regular merge instead.
  • Manually start the release action for the main branch via GitHub UI

Screenshot 2022-10-10 at 09 05 32

Clone this wiki locally