Skip to content

Latest commit

 

History

History
146 lines (100 loc) · 5 KB

CONTRIBUTING.md

File metadata and controls

146 lines (100 loc) · 5 KB
Raw

Contributing

Filing an Issue

If you are trying to use this application and its libraries and run into an issue - please file an issue! We'd love to get you up and running, even if the issue you have might not be directly be related to this project's own code base.

When filing an issue, do your best to be as specific as possible. Use a short and concise title that fits into a single line. Like any good commit message titles don't end with a period ;) Add a comprehensive description that explains your motivation and includes steps to reproduce exceptional behaviour in case of a bug.

Writing Code

Follow the API Guidelines

All code written in Rust should follow the Rust API Guidelines.

Use existing code as a template, but do not copy it blindly. Remember that code, even when written by the most experienced contributor long ago, might not comply with the current version of the guide. When in doubt don't hesitate to ask for help or advice.

Use the stable Toolchain

Use the rustup override command to make sure that you are using the stable toolchain. Run this command in the aoide-rs directory you cloned.

rustup override set stable

Keep Rust and all Components up-to-date

We closely follow all updates of stable Rust and its components. Keep your installation up-to-date with the following command:

rustup update stable

Format the Code

Before submitting code in a PR, make sure that you have formatted the codebase using rustfmt. rustfmt is a tool for formatting Rust code, which helps keep style consistent across the project.

If you have not already configured rustfmt for the stable toolchain, install the most recent version of rustfmt using this command:

rustup component add rustfmt-preview --toolchain stable

To run rustfmt, use this command:

cargo fmt

You can configure a git pre-commit hook (see Customizing Git - Git Hooks) to make sure you only commit properly formatted code. This hook emits an error when code is not formatted according to rustfmt or tests fail.

Check the Coding Style

You should regularly check your coding style with Clippy avoid common pitfalls and get the most out of Rust. This might not work as expected at any time until Clippy finally becomes available in the stable toolchain.

First update your nightly toolchain:

rustup update nightly

Then install the most recent version of Clippy:

rustup component add clippy-preview --toolchain=nightly

To check the coding style, use this command:

cargo +nightly clippy

Committing Changes

Keep your change sets small per commit:

  • Revert any unnecessary changes or changes to unrelated files
  • Use separate commits when moving or renaming files and when fixing formatting issues with rustfmt
  • Don't accidentally check in any temporary files

Make sure that the code compiles without errors. The only exception is allowed for tests that might neither compile nor succeed for an intermediate commit.

Try really hard to follow The seven rules of a great Git commit message:

  1. Separate subject from body with a blank line
  2. Limit the subject line to 50 characters
  3. Capitalize the subject line
  4. Do not end the subject line with a period
  5. Use the imperative mood in the subject line
  6. Wrap the body at 72 characters
  7. Use the body to explain what and why vs. how

The Atom editor has built-in syntax highlighting for git commit messages. You may use it to help your commit messages comply with the rules above. Check out how to configure Atom to be your Git commit editor.

Submitting a Merge Request (MR)

If you are considering to submit a merge request, make sure that there's an issue filed for the work you'd like to do. There might be some discussion required! Filing an issue first helps to ensure that the work you put into your merge request is acceptable for all participants of the project and will get merged. :)

Before you submit your merge request, check that you have completed all of the steps and followed the rules mentioned above in Writing Code. Finally link the issue that your merge request is responding to in the descriptive text of the MR.

Conduct

We follow the Rust Code of Conduct.