Thank you for considering contributing to LionAGI! This document provides guidelines and instructions for contributing to this project.
-
Fork the Repository: Begin by forking the repository to your GitHub account. This creates your own copy of the project where you can make changes.
-
Clone the Forked Repository: Clone the repository to your local machine to start working on the changes.
-
Set Up Your Development Environment: Ensure you have a suitable Python development environment. Any IDE that supports Python and package installation should be sufficient.
-
Creating Branches: For new features or bug fixes, create a new branch off the main branch. Branch names should be descriptive and reflect the feature or fix you are working on.
-
Commit Messages: Write clear and descriptive commit messages. While there’s no strict format, ensure your messages convey the purpose of the commit.
-
Pull Requests: Once you are ready with your changes, push your branch to your fork and open a pull request against the main repository.
-
Pull Request Description: Provide a detailed description of the changes in your pull request. Link it to any relevant issues.
-
Code Review Process: Your pull request will be reviewed by the project maintainers. Feedback may be provided for improvements.
-
Merging: After approval, one of the maintainers will merge your pull request. No direct merges into the main branch are allowed without approval.
-
Writing Tests: Include unit and integration tests for your code. Ensure your tests cover new features as well as any changes to existing functionality.
-
Running Tests Locally: Before submitting your pull request, run all tests locally to ensure they pass.
-
PEP 8: Follow PEP 8 style guidelines for writing Python code.
-
PEP 257: Adhere to PEP 257 for docstring conventions.
-
Linting: Use linters to check your code against these standards.
- Managing Dependencies: Do not add or update dependencies without prior approval from the maintainers.
-
Update Documentation: Accompany your code changes with corresponding updates in the documentation.
-
Versioning Documentation: Documentation should be versioned alongside the code.
- Using Discord: Use the project’s Discord for discussions, questions, and collaboration.
-
Recognition: We value your contributions and will acknowledge significant contributions in our social media and release notes.
-
GitHub Sponsors: We are considering setting up a GitHub Sponsor button to enable sponsorship for our contributors.
If you have any questions or need further clarification about contributing, feel free to reach out on our Discord server.
Thank you for contributing to LionAGI, and we look forward to your contributions!