caicancai commented on code in PR #1687: URL: https://github.com/apache/iggy/pull/1687#discussion_r2066788413
########## CONTRIBUTING.md: ########## @@ -0,0 +1,77 @@ +# Contributing + +First, thank you for contributing to Iggy! The goal of this document is to provide everything you need to start contributing to Iggy. The following TOC is sorted progressively, starting with the basics and expanding into more specifics. + +## Your First Contribution + +1. Ensure your change has an issue! Find an [existing issue](https://github.com/apache/iggy/issues) or open a new issue. +1. [Fork the Iggy repository](https://github.com/apache/Iggy/fork) in your own GitHub account. +1. [Create a new Git branch](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository). +1. Make your changes. +1. [Submit the branch as a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) to the master Iggy repo. An Iggy team member should comment and/or review your pull request within a few days. Although, depending on the circumstances, it may take longer. + +## Workflow + +### Git Branches + +*All* changes must be made in a branch and submitted as [pull requests](#github-pull-requests). Iggy does not adopt any type of branch naming style, but please use something descriptive of your changes. + +### GitHub Pull Requests + +Once your changes are ready you must submit your branch as a [pull request](https://github.com/apache/Iggy/pulls). + +#### Title + +The pull request title must follow the format outlined in the [conventional commits spec](https://www.conventionalcommits.org). [Conventional commits](https://www.conventionalcommits.org) is a standardized format for commit messages. Iggy only requires this format for commits on the `master` branch. And because Iggy squashes commits before merging branches, this means that only the pull request title must conform to this format. + +The following are all good examples of pull request titles: + +```text +fix(ci): add Cross.toml for CI builds +chore(repo): add ASF license header to all the files +refactor(server): remove redundant sha1 print +chore(docs): add contributing guide +refactor(server): remove redundant sha1 print +``` + +#### Reviews & Approvals + +All pull requests should be reviewed by at least two Iggy committer. + +#### Merge Style + +All pull requests are squash merged. +We generally discourage large pull requests that are over 300–500 lines of diff. +If you would like to propose a change that is larger, we suggest +coming onto our [Discussions](https://github.com/apache/Iggy/discussions) and discussing it with us. +This way we can talk through the solution and discuss if a change that large is even needed! +This will produce a quicker response to the change and likely produce code that aligns better with our process. + +### CI + +Currently, Iggy uses GitHub Actions to run tests. The workflows are defined in `.github/workflows`. + +## Setup + +### Bring your own toolbox + +Iggy is primarily a Rust project. To build Iggy, you will need to set up Rust development first. We highly recommend using [rustup](https://rustup.rs/) for the setup process. + +For Linux or macOS, use the following command: + +```shell +curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh +``` + +For Windows, download `rustup-init.exe` from [here](https://win.rustup.rs/x86_64) instead. + +Rustup will read Iggy's `rust-toolchain.toml` and set up everything else automatically. To ensure that everything works correctly, run `cargo version` under Iggy's root directory: + +```shell +$ cargo version +cargo 1.69.0 (6e9a83356 2023-04-12) Review Comment: done ########## CONTRIBUTING.md: ########## @@ -0,0 +1,77 @@ +# Contributing + +First, thank you for contributing to Iggy! The goal of this document is to provide everything you need to start contributing to Iggy. The following TOC is sorted progressively, starting with the basics and expanding into more specifics. + +## Your First Contribution + +1. Ensure your change has an issue! Find an [existing issue](https://github.com/apache/iggy/issues) or open a new issue. +1. [Fork the Iggy repository](https://github.com/apache/Iggy/fork) in your own GitHub account. +1. [Create a new Git branch](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository). +1. Make your changes. +1. [Submit the branch as a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) to the master Iggy repo. An Iggy team member should comment and/or review your pull request within a few days. Although, depending on the circumstances, it may take longer. + +## Workflow + +### Git Branches + +*All* changes must be made in a branch and submitted as [pull requests](#github-pull-requests). Iggy does not adopt any type of branch naming style, but please use something descriptive of your changes. + +### GitHub Pull Requests + +Once your changes are ready you must submit your branch as a [pull request](https://github.com/apache/Iggy/pulls). + +#### Title + +The pull request title must follow the format outlined in the [conventional commits spec](https://www.conventionalcommits.org). [Conventional commits](https://www.conventionalcommits.org) is a standardized format for commit messages. Iggy only requires this format for commits on the `master` branch. And because Iggy squashes commits before merging branches, this means that only the pull request title must conform to this format. + +The following are all good examples of pull request titles: + +```text +fix(ci): add Cross.toml for CI builds +chore(repo): add ASF license header to all the files +refactor(server): remove redundant sha1 print +chore(docs): add contributing guide +refactor(server): remove redundant sha1 print +``` + +#### Reviews & Approvals + +All pull requests should be reviewed by at least two Iggy committer. Review Comment: done -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
