Thanks for wanting to contribute! There are many ways to contribute and we appreciate any level you're willing to do.
To get started checkout issues labeled "help wanted" and "good first issue"
As a heads up, we'll be running your PR through the following CI jobs:
- warnings turned to compile errors
cargo testrustfmt(we recommend to setup runningrustfmton file save)clippy
When we're ready to release, a project owner should do the following:
- Create(checkout) a release branch (naming convention
release/vX-Y-Zusing theergo-libversion); - install or update "cargo release" (via
cargo install cargo-release); cargo release minor --no-dev-version -vvif you intend to bump a minor version or changeminortomajorto bump a major version,patchto bump a patch/hotfix version (you might want to add any crates without changes to--excludeoption list, e.g.sigma-ser,sigma-util, etc.)- check the output and run it with
--executeto actually execute it(make sure that you have api token fromcrates.io, otherwise runcargo loginfirst); - Build and publish npm package (
cd bindings/ergo-lib-wasm && npm run publish-nodejs && npm run publish-browser); - Merge release branch into develop
- Merge release branch into master
- Make a github release