Skip to content

Commit

Permalink
Merge branch '0xPlaygrounds:main' into bubba
Browse files Browse the repository at this point in the history
  • Loading branch information
crStiv authored Feb 5, 2025
2 parents a3deab2 + e86d1b4 commit 39ce2bc
Show file tree
Hide file tree
Showing 96 changed files with 11,418 additions and 737 deletions.
16 changes: 16 additions & 0 deletions .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,22 @@ jobs:
- name: Run cargo fmt
run: cargo fmt -- --check

# Special check to make sure rig-core is compatible with the wasm target
check-wasm:
name: stable / check rig-core wasm target
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4

- name: Install Rust stable
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
target: wasm32-unknown-unknown

- name: Run cargo check wasm target
run: cargo check --package rig-core --features worker --target wasm32-unknown-unknown

clippy:
name: stable / clippy
runs-on: ubuntu-latest
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Before reporting an issue, please check existing or similar issues that are curr

Contributions are always encouraged and welcome. Before creating a pull request, create a new issue that tracks that pull request describing the problem in more detail. Pull request descriptions should include information about it's implementation, especially if it makes changes to existing abstractions.

PRs should be small and focused and should avoid interacting with multiple facets of the library. This may result in a larger PR being split into two or more smaller PRs. Commit messages should follow the [Conventional Commit](conventionalcommits.org/en/v1.0.0) format (prefixing with `feat`, `fix`, etc.) as this integrates into our auto-releases via a [release-plz](https://github.com/MarcoIeni/release-plz) Github action.
PRs should be small and focused and should avoid interacting with multiple facets of the library. This may result in a larger PR being split into two or more smaller PRs. Commit messages should follow the [Conventional Commit](https://conventionalcommits.org/en/v1.0.0) format (prefixing with `feat`, `fix`, etc.) as this integrates into our auto-releases via a [release-plz](https://github.com/MarcoIeni/release-plz) Github action.

**Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://kcd.im/pull-request)

Expand Down
Loading

0 comments on commit 39ce2bc

Please sign in to comment.