clockworklabs / clockworklabs/SpacetimeDB

Run CI on SpacetimeDBPrivate against SpacetimeDB changes

Open
#359 0 comments 0 reactions 2 assignees View on GitHub

@kim is already working on this.

Since Oct 3, 2023.

Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

SpacetimeDBPrivate can regress too far if the submodule isn't tested with SpacetimeDB quickly enough. We should add some CI to check whether the compilation fails or not or somehow figure out how to test SpacetimeDBPrivate w/ up to date changes in SpacetimeDB.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.