Skip to content

Latest commit

 

History

History
67 lines (45 loc) · 3.17 KB

CONTRIBUTING.md

File metadata and controls

67 lines (45 loc) · 3.17 KB

Contributing to Alpaca-Turbo

First off, thank you for considering contributing to Alpaca-Turbo! We appreciate your effort and time to make this project better. This document provides guidelines and instructions for contributing to the project.

Table of Contents

Code of Conduct

By participating in this project, you are expected to uphold our Code of Conduct.

Getting Started

  1. Fork the repository and clone it to your local machine.
  2. Set up the development environment by following the instructions in the README file.
  3. Explore the codebase, run tests, and verify that everything works as expected.

How to Contribute

Reporting Bugs

If you find any bugs or issues, please report them by opening a new issue on GitHub. When reporting a bug, please provide the following information:

  • A clear and descriptive title.
  • A detailed description of the issue and steps to reproduce it.
  • The expected behavior and the actual behavior.
  • Any error messages or logs related to the issue.
  • The version of the software you are using.

Suggesting Enhancements

If you have ideas for new features or enhancements, we would love to hear them! Please open a new issue on GitHub and describe your suggestion in detail.

Submitting Pull Requests

  1. Create a new branch for your feature or bugfix. Use a descriptive name like feature/your-feature-name or fix/your-bugfix-name.
  2. Make your changes, following the Style Guidelines below.
  3. Test your changes and ensure that they don't introduce new issues or break existing functionality.
  4. Commit your changes, following the commit message guidelines.
  5. Push your branch to your fork on GitHub.
  6. Open a new pull request against the main branch of the Wolverine repository. Include a clear and concise description of your changes, referencing any related issues.

Style Guidelines

Code Style

Wolverine uses PEP 8 as its code style guide. Please ensure that your code follows these guidelines. We recommend using a linter like flake8 to check your code style before committing.

Commit Messages

Write clear and concise commit messages that briefly describe the changes made in each commit. Use the imperative mood and start with a capitalized verb, e.g., "Add new feature" or "Fix bug in function".

Additional Resources