Skip to content

Latest commit

 

History

History
24 lines (18 loc) · 1.65 KB

CONTRIBUTING.md

File metadata and controls

24 lines (18 loc) · 1.65 KB
Raw

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.

hacking

Just a few simple items to keep in mind as you hack.

  • Pull request early and often. This helps to let others know what you are working on. Please use Github's Draft PR mechanism if your PR is not yet ready for review.
  • Remember to update the CHANGELOG.md once you believe your work is nearing completion.

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 for versioning this system.

  • update Cargo.toml version & execute cargo update — this ensures that the Cargo.lock doesn't update during CI due to the new version number, which will cause CI failure.
  • 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, and will upload release artifacts to the release page. Verify that this process has completed successfully.
  • update the new release page with details on the changes made, which should reflect the content of the CHANGELOG.md.