airlab-web 0.1.3

airlab backend
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

# Contributing to airlab-rs

Thank you for your interest in contributing to airlab-rs! We welcome contributions from the community and appreciate your help in making this project better.

## How to Contribute

### Reporting Issues

If you find a bug, have a question, or want to request a feature, please open an issue on our [GitHub repository](https://github.com/BodenmillerGroup/airlab-rs/issues). Provide as much detail as possible to help us understand and address the issue efficiently.

### Submitting Code Changes

1. **Fork the Repository**: Click the “Fork” button on the GitHub repository.
2. **Clone Your Fork**: Clone your forked repository to your local machine.
   ```sh
   git clone https://github.com/BodenmillerGroup/airlab-rs.git
   cd airlab-rs
   ```
3. **Create a Branch**: Use a descriptive name for your branch.
   ```sh
   git checkout -b feature-name
   ```
4. **Make Your Changes**: Write clear and concise code with comments where necessary.
5. **Run Tests**: Ensure that all tests pass before submitting your changes.
   ```sh
   cargo test
   ```
6. **Commit Your Changes**: Use a clear and descriptive commit message.
   ```sh
   git commit -m "Add feature X to airlab-rs"
   ```
7. **Push Your Branch**: Push your changes to your fork.
   ```sh
   git push origin feature-name
   ```
8. **Create a Pull Request**: Open a pull request (PR) on the main repository and describe your changes.

### Code Style Guidelines

- Follow Rust’s standard formatting (`cargo fmt`).
- Ensure your code follows best practices and is idiomatic.
- Use `clippy` to check for common mistakes (`cargo clippy`).

### Reviewing and Merging

- PRs will be reviewed by maintainers.
- Address any feedback given in the review.
- Once approved, maintainers will merge your PR.

## Community and Code of Conduct

By contributing, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).

## License

By contributing to airlab-rs, you agree that your contributions will be licensed under the [MIT License](LICENSE).

---

We appreciate your time and effort in making airlab-rs better. Happy coding!