CI updates.

Author: thedodd

.github/workflows/ci.yaml

@@ -12,11 +12,15 @@ jobs:
           toolchain: stable
           target: wasm32-unknown-unknown
           default: true
-          components: clippy
+          components: clippy, rustfmt
       - uses: actions-rs/cargo@v1
         with:
           command: clippy
           args: -- -D warnings
+      - uses: actions-rs/cargo@v1
+        with:
+          command: fmt
+          args: -- --check
       - uses: actions-rs/cargo@v1
         with:
           command: build

.github/workflows/release.yaml

@@ -0,0 +1,32 @@
+name: release
+on:
+  push:
+    tags:
+    - 'v*'
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    outputs:
+      upload_url: ${{ steps.create_release.outputs.upload_url }}
+    steps:
+      - uses: actions/checkout@v2
+      - run: echo ::set-env name=RELEASE_VERSION::${GITHUB_REF#refs/*/}
+      - uses: actions-rs/toolchain@v1
+        with:
+          toolchain: stable
+      - uses: actions-rs/cargo@v1
+        with:
+          command: build
+          args: --release
+      - name: create release
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          tag_name: ${{ github.ref }}
+          release_name: ${{ github.ref }}
+          body: ""
+          draft: true
+          prerelease: false

CONTRIBUTING.md

@@ -0,0 +1,19 @@
+contributing
+============
+We are all living beings, and what is most important is that we respect each other and work together. If you can not uphold this simple standard, then your contributions are not welcome.
+
+## linting
+We are using clippy & rustfmt. Clippy is SO GREAT! Rustfmt ... has a lot more growing to do; however, we are using it for uniformity.
+
+Please be sure that you've configured your editor to use clippy & rustfmt, or execute them manually before submitting your code. CI will fail your PR if you do not.
+
+## release workflow
+We follow [semver](https://semver.org/spec/v2.0.0.html) for versioning this system.
+
+- [ ] update `Cargo.toml` `version`.
+- [ ] ensure CI completes successfully.
+- [ ] add a new tag to the repo matching the new `Cargo.toml` `version`. Either via `git tag` or via the Github UI.
+    - all release tags should start with the letter `v` followed by a semver version.
+- [ ] CI is configured for release tags and will create a new Github release.
+- [ ] once CI for the tag has finished successfully, update the new release page with details on the changes made, which should reflect the content of the `CHANGELOG.md`.
+- [ ] lastly, `cargo publish`.