Skip to content

Latest commit

 

History

History
45 lines (30 loc) · 1.85 KB

CONTRIBUTING.md

File metadata and controls

45 lines (30 loc) · 1.85 KB

Contributing to Caliban

First off, thanks for taking the time to contribute! 🎉 The following is a set of guidelines for contributing to Caliban.

Code of Conduct

This project and everyone participating in it is governed by the Caliban Code of Conduct. By participating, you are expected to uphold this code.

How Can I Contribute?

Reporting Bugs

If you find a bug, please report it by opening a new issue in the Issues section and include:

  • A clear and descriptive title.
  • A detailed description of the problem.
  • Steps to reproduce the issue.
  • Any relevant logs, screenshots, or files that may help us understand the issue.

Suggesting Features

If you have an idea for a new feature, please suggest it by opening a new issue in the Issues section and include:

  • A clear and descriptive title.
  • A detailed description of the feature.
  • Any relevant sample code, diagrams, or screenshots.

Submitting Changes

  1. Fork the repository.
  2. Create a new branch (git checkout -b feature/YourFeature).
  3. Make your changes.
  4. Format your code using the fmt command in sbt.
  5. Ensure all tests pass.
  6. Commit your changes (git commit -m 'Add some feature').
  7. Push to the branch (git push origin feature/YourFeature).
  8. Open a pull request. It will trigger the CI to run various with different Scala versions and platforms.

Additional Notes

  • If you have questions or need help, feel free to ask on our Discord channel or open an issue.
  • Before starting to work on a major change, please open an issue to discuss your proposed changes to ensure they fit within the project's scope and are not already being worked on.

Thank you for contributing to Caliban!