Contributing to GenAI 🌟

We're thrilled that you're interested in contributing to GenAI! Your contributions are essential for making GenAI better. Here are the guidelines to help you get started. 🚀

Code of Conduct 📜

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

How to Contribute 🤔

You can contribute in many ways:

Reporting Bugs 🐛

Bugs are tracked as GitHub issues. When you are creating a bug report, please include as many details as possible:

Use a clear and descriptive title for the issue to identify the problem. 🏷️
Describe the exact steps which reproduce the problem in as many details as possible. 📝
Provide specific examples to demonstrate the steps. 🔍
Describe the behavior you observed after following the steps and why you find this behavior problematic. 🤔
Explain which behavior you expected to see instead and why. ✨

Suggesting Enhancements 💡

Enhancement suggestions are also tracked as GitHub issues. When suggesting an enhancement:

Use a clear and descriptive title for the issue to identify the suggestion. 🏷️
Provide a step-by-step description of the suggested enhancement in as many details as possible. 📝
Provide specific examples to demonstrate the steps or provide mock-ups. 🔍
Explain why this enhancement would be useful to GenAI users. 🌈

Your First Code Contribution 👶

Unsure where to begin contributing to GenAI? You can start by looking through the beginner and help-wanted issues:

Beginner issues - issues which should only require a few lines of code, and a test or two. 🌱
Help wanted issues - issues which should be a bit more involved than beginner issues. 🆘

Pull Requests 👐

Fill in the required template. 📃
Do not include issue numbers in the PR title. ❌
Include screenshots and animated GIFs in your pull request whenever possible. 📸
Follow the Python styleguides. 🐍
Include thoughtfully-worded, well-structured tests. Mock external services and cover all use cases. 🧪
Document new code based on the Documentation Styleguide. 📚
End files with a newline. ↩️
Avoid platform-dependent code. 💻

Git Commit Messages 📝

Use the present tense ("Add feature" not "Added feature"). ✅
Use the imperative mood ("Move cursor to..." not "Moves cursor to..."). 🎯
Limit the first line to 72 characters or less. 📏
Reference issues and pull requests liberally after the first line. 🔗

Pull Request Process 🔄

The pull request will be merged after review by a core team member. ✔️

Community Guidelines and Code of Conduct 🌍

We are committed to building a welcoming, inclusive, and respectful community. Here are some key points to remember:

Be kind and courteous to everyone. 😊
Respect differing viewpoints and experiences. 🤝
Give and gracefully accept constructive feedback. 🌟
Focus on what is best for the community. 🌈

For a more detailed set of guidelines, please refer to our Code of Conduct, which outlines our expectations for participants, as well as the consequences for unacceptable behavior.

We hope these guidelines help make your experience a fruitful and enjoyable one.