Contribution Guidelines¶
Welcome! This guide provides all the details you need to contribute effectively to the project. Thank you for helping us make octotask a better tool for developers worldwide. 💡
📋 Table of Contents¶
- Code of Conduct
- How Can I Contribute?
- Pull Request Guidelines
- Coding Standards
- Development Setup
- Testing
- Deployment
- Docker Deployment
- VS Code Dev Containers Integration
🛡️ Code of Conduct¶
This project is governed by our Code of Conduct. By participating, you agree to uphold this code. Report unacceptable behavior to the project maintainers.
🛠️ How Can I Contribute?¶
1️⃣ Reporting Bugs or Feature Requests¶
- Check the issue tracker to avoid duplicates.
- Use issue templates (if available).
- Provide detailed, relevant information and steps to reproduce bugs.
2️⃣ Code Contributions¶
- Fork the repository.
- Create a feature or fix branch.
- Write and test your code.
- Submit a pull request (PR).
3️⃣ Join as a Core Contributor¶
✅ Pull Request Guidelines¶
PR Checklist¶
- Branch from the main branch.
- Update documentation, if needed.
- Test all functionality manually.
- Focus on one feature/bug per PR.
Review Process¶
- Manual testing by reviewers.
- At least one maintainer review required.
- Address review comments.
- Maintain a clean commit history.
📏 Coding Standards¶
General Guidelines¶
- Follow existing code style.
- Comment complex logic.
- Keep functions small and focused.
- Use meaningful variable names.
🖥️ Development Setup¶
1️⃣ Initial Setup¶
- Clone the repository:
- Install dependencies:
- Set up environment variables:
- Rename
.env.example
to.env.local
. - Add your API keys:
- Optionally set:
- Debug level:
VITE_LOG_LEVEL=debug
- Context size:
DEFAULT_NUM_CTX=32768
- Debug level:
Note: Never commit your .env.local
file to version control. It's already in .gitignore
.