Skip to content

Latest commit

 

History

History
58 lines (39 loc) · 2.42 KB

CONTRIBUTING.md

File metadata and controls

58 lines (39 loc) · 2.42 KB

Contributing

Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.

Contributions to this project are released to the public under the project's open source license.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Prerequisites for running and testing code

We recommend that you install Rust with the rustup tool. twirp-rs targets stable Rust versions.

Submitting a pull request

  1. Fork and clone the repository.
  2. Install protoc with your package manager of choice.
  3. Build the software: cargo build.
  4. Create a new branch: git checkout -b my-branch-name.
  5. Make your change, add tests, and make sure the tests and linter still pass.
  6. Push to your fork and submit a pull request.
  7. Pat yourself on the back and wait for your pull request to be reviewed and merged.

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

  • Write tests.
  • Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
  • Write a good commit message.

Setting up a local build

Make sure you have rust toolchain installed on your system and then:

cargo build && cargo test

Run clippy and fix any lints:

make lint

Releasing

  1. Go to the Create Release PR action and press the button to run the action. This will use release-plz to create a new release PR.
  2. Adjust the generated changelog and version number(s) as necessary.
  3. Get PR approval
  4. Merge the PR. The publish-release.yml workflow will automatically publish a new release of any crate whose version has changed.

Resources