This repository contains a set of libraries that help you build robust highly scalable services in Rust.
- Every PR submitted to this repo should follow the Conventional Commits specification.
- Every crate built in this repo should:
- Have an entry in the Crates section above.
- Have an entry in in CHANGELOG.md.
- Have a README.md file generated using
cargo-rdmewith a consistent set of badges (see crates/data_privacy/README.md as an example) - Have a CHANGELOG.md file generated using
git-cliff. - Have a meaningful set of categories and keywords in their Cargo.toml file (see crates/data_privacy/Cargo.toml as an example). The
oxidizerkeyword should always be present.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Releases to crates.io are handled by an internal process. To release a new version of any of the crates, bump the version in accordance to semver. You should use cargo set-version for this to ensure all appropriate files are updated. For example:
cargo set-version -p data_privacy_macros -p data_privacy --bump minorAfter the version is bumped, an automated process should publish a new version within the next 48 hours.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.