Skip to main content

Development

When developing HivePrint modules, keep the following in mind.

  1. We use a private registry for HivePrint Pi.
  2. We use a public registry for Create Hiveprint Starter.
  3. You must build, and then version, and then publish.
  4. Use conventional commits.
  5. Rebase your feature branches off main.
  6. There is no production, main is production, and tagging is the ideal flow*
    1. At time of writing, we may have not yet implemented this.

We use changesets for handling changes.

Versioning​

The public channel is latest. Anyone on the public channel gets fully tested code that has been released.

The beta test channel next. Anyone on the next channel gets things that have been approved in house.

The internal testing channel is testing. Anyone on this channel should be wary of updates, as things will be unstable.